Neotoma with OpenCode

• →Local agent runtime for code editing, shell work, and project tasks
• →Plugin hooks for sessions, messages, tool execution, shell environment, and compaction context
• →Load plugins from opencode.json (npm packages) or from local files under .opencode/plugins/ and ~/.config/opencode/plugins/

• ×Durable structured memory shared across other agent tools
• ×Entity resolution, observation history, or provenance-backed facts
• ×A persistence or consistency layer for external stores: OpenCode runs hooks and tool calls but does not verify, deduplicate, sequence, or repair what lands in databases, APIs, or files; that remains the job of plugins and integrations you add

• →Persistent memory graph shared with Cursor, Claude Code, Codex, ChatGPT, and OpenClaw
• →Conversation, message, tool, and compaction observations with stable provenance
• →Structured state written by the agent through MCP, with hook capture as a safety net
• →CLI fallback when MCP is unavailable or the agent needs direct terminal access

OpenCode stays responsible for the agent runtime. Neotoma stays responsible for the durable state layer. MCP remains the quality path for schema-typed writes, while the OpenCode plugin records baseline turn activity when the agent misses a step.

The Neotoma OpenCode plugin is published as @neotoma/opencode-plugin. Add it to opencode.json:

{
  "plugin": ["@neotoma/opencode-plugin"]
}

OpenCode installs npm plugins automatically at startup. For local plugin files, export a named plugin function from ~/.config/opencode/plugins/neotoma.ts:

import neotoma from "@neotoma/opencode-plugin";

export const Neotoma = neotoma();

Start Neotoma locally, then let OpenCode load the plugin from npm or a local plugin file:

npm install -g neotoma
neotoma api start --background --env dev

Keep MCP configured as well. Hooks guarantee baseline capture; MCP gives the agent the richer store, retrieval, relationship, and feedback tools.

• →Plugins (npm plugins, local files, and hook events)
• →SDK (client APIs exposed to plugin context)

Once Neotoma is running, try these starter commands in OpenCode to see cross-session memory in action: