21 lines
1012 B
YAML
Raw Permalink Normal View History

name: scribase
feat: add scribase_memory_task — real persistent agent memory (store/recall/search/forget) Hermes agents had no persistent memory via this plugin: scribase_query is read-only (enforced by the control plane itself) and scribase_lint_migration hardcodes apply:false, so none of the first four tools could ever write application data, only inspect or lint it. scribase_memory_task closes that gap using a real, previously-unused endpoint read from the compiled control plane: POST .../database/execute (the write-mode SQL route the Scribase Studio SQL editor uses in "write mode", crates/control-api/src/adapters/sql_execute.rs), for store/forget; recall/search reuse the existing read-only database/query route. Creates its own table (hermes_agent_memories, RLS enabled) on first use, scoped by an optional namespace so multiple agents/users can share a project without reading each other's memories. Every value interpolated into SQL (content, metadata, scope, memory_id) is escaped via the standard Postgres string-literal escape (_sql_literal) — the model never passes raw SQL through this tool. Verified: a throwaway monkeypatched test exercises all 4 actions + error paths + an injection-style content string (confirms balanced escaping, no executable SQL smuggled through). Then ran the real, unmodified tools.py directly against a real, no-login temporary Scribase project on production api.scribase.com: store (x2) -> recall -> search -> scope-isolation check (a second, never-used scope correctly returns zero rows) -> forget -> recall again (confirms exactly the forgotten memory is gone, the other survives). Full transcript in HACKATHON-SUBMISSION-2026-11-05.md. Re-ran validate_plugin_dir() (the function `hermes plugins validate` calls) against a fresh NousResearch/hermes-agent clone: 15/15 checks pass, 0 warnings, isolation host_ready: true, declared tools matches registrations (5 tools, including scribase_memory_task). plugin.yaml bumped to 1.3.0, provides_tools now lists all 5.
2026-11-06 18:16:17 +03:00
version: "1.3.0"
description: "Provision a hosted Postgres backend project on Scribase (api.scribase.com), lint a SQL migration for real safety issues (missing RLS, unsafe grants/policies) before running it, run read-only queries against the project's database, give an agent a real copy-on-write Postgres branch to create, promote, or discard for one task, and give the agent real persistent memory (store/recall/search/forget) backed by a Postgres table in its own project."
author: Scribase
requires_hermes: ">=0.20.1"
provides_tools:
- scribase_create_project
- scribase_lint_migration
- scribase_query
feat: add scribase_branch_task — real copy-on-write branch create/promote/discard Fourth tool: one action='create'|'promote'|'discard' tool that forks a real copy-on-write Postgres branch for one agent task (POST /v1/environments, kind="preview", bounded TTL so it always lands in the control plane's agent-branch slot pool), three-way merges it back into its parent on action='promote' (POST .../branches/merge, reads the real applied/clean/changes/conflicts/statements fields the compiled server renders, and surfaces a real mfa_required rejection on a forced merge instead of hiding it), or deletes it outright on action='discard' (DELETE .../environments/{env}). Built from the real control-api source (http/environments.rs, http/branches.rs, adapters/branch.rs, adapters/usage.rs::AGENT_BRANCH_MAX_TTL_HOURS) and the public docs.scribase.com environments/branches pages, not guessed. Factored create_project's polling and API-keys/connection readback into shared _poll_operation/_read_environment_access helpers, reused by both tools; create_project's own behavior is unchanged (verified with a mocked HTTP layer, happy path and warning path). plugin.yaml bumped to 1.2.0, provides_tools now lists all 4 tools. README rewritten with a one-line pitch, a demo-video pointer, and a real example call + example response for every tool. HACKATHON-SUBMISSION updated with the new tool, a fresh validator run (15/15, 0 warnings), and an honest demo-coverage note for the branch-task tool including two live production responses from the real public /v1/demo/branch endpoint this tool's workflow mirrors (a transient 402, then the real 429 per-hour rate limit — both genuine, neither invented).
2026-11-05 23:48:28 +03:00
- scribase_branch_task
feat: add scribase_memory_task — real persistent agent memory (store/recall/search/forget) Hermes agents had no persistent memory via this plugin: scribase_query is read-only (enforced by the control plane itself) and scribase_lint_migration hardcodes apply:false, so none of the first four tools could ever write application data, only inspect or lint it. scribase_memory_task closes that gap using a real, previously-unused endpoint read from the compiled control plane: POST .../database/execute (the write-mode SQL route the Scribase Studio SQL editor uses in "write mode", crates/control-api/src/adapters/sql_execute.rs), for store/forget; recall/search reuse the existing read-only database/query route. Creates its own table (hermes_agent_memories, RLS enabled) on first use, scoped by an optional namespace so multiple agents/users can share a project without reading each other's memories. Every value interpolated into SQL (content, metadata, scope, memory_id) is escaped via the standard Postgres string-literal escape (_sql_literal) — the model never passes raw SQL through this tool. Verified: a throwaway monkeypatched test exercises all 4 actions + error paths + an injection-style content string (confirms balanced escaping, no executable SQL smuggled through). Then ran the real, unmodified tools.py directly against a real, no-login temporary Scribase project on production api.scribase.com: store (x2) -> recall -> search -> scope-isolation check (a second, never-used scope correctly returns zero rows) -> forget -> recall again (confirms exactly the forgotten memory is gone, the other survives). Full transcript in HACKATHON-SUBMISSION-2026-11-05.md. Re-ran validate_plugin_dir() (the function `hermes plugins validate` calls) against a fresh NousResearch/hermes-agent clone: 15/15 checks pass, 0 warnings, isolation host_ready: true, declared tools matches registrations (5 tools, including scribase_memory_task). plugin.yaml bumped to 1.3.0, provides_tools now lists all 5.
2026-11-06 18:16:17 +03:00
- scribase_memory_task
requires_env:
- name: SCRIBASE_API_KEY
description: "Scribase organization API key. Create one under Organization -> API tokens in the Scribase console, or via POST /v1/organizations/{org}/api-keys."
url: "https://docs.scribase.com/docs/api"
secret: true
config_schema:
api_base_url:
type: str
required: false