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.
21 lines
1012 B
YAML
21 lines
1012 B
YAML
name: scribase
|
|
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
|
|
- scribase_branch_task
|
|
- 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
|