Set up OpenCode with a knowledge graph of your codebase

OpenCode is an open-source terminal agent, and Graphify meets it with an equally open-source integration: a local knowledge graph in graphify-out/, wired in through two native OpenCode mechanisms. Always-on rules go in AGENTS.md, and a small JavaScript plugin, registered through opencode.json, reminds the agent the graph exists the first time it reaches for bash. Both are plain project files you can read, commit, and diff.

What graphify opencode install writes

• An AGENTS.md section: query-first rules in your project's AGENTS.md, the file OpenCode reads in every session. The installer owns only its own section; the rest of the file is untouched.
• A plugin: .opencode/plugins/graphify.js, hooking OpenCode's tool.execute.before event.
• A registration in .opencode/opencode.json, appending the plugin to the "plugin" array (existing config is preserved).
• The skill: ~/.config/opencode/skills/graphify/SKILL.md globally, or .opencode/skills/graphify/SKILL.md with --project. This is what /graphify triggers.

{  "plugin": [".opencode/plugins/graphify.js"]}

One gotcha before you start

The bare graphify install command targets Claude Code by design. That matters here because a natural move is to ask the OpenCode agent itself to install Graphify, and if it runs the bare command, you end up with Claude Code files under ~/.claude/ and no OpenCode wiring at all. Always use the platform-specific command:

$ uv tool install graphifyy$ graphify opencode install

(graphify install --platform opencode is equivalent; add --project to keep the skill inside the repo.) If the bare command already ran, nothing is broken: run graphify claude uninstall to drop the unwanted pieces, then graphify opencode install.

Build the graph, then ask

Type /graphify . in an OpenCode session. The skill maps the project into graphify-out/: graph.json (the queryable graph), graph.html (interactive view), and GRAPH_REPORT.md (highlights and suggested questions). From then on, structural questions route through graphify query "<question>" (a scoped subgraph), graphify path "<A>" "<B>" (the dependency route between two symbols), and graphify explain "<concept>"(one node's full neighborhood). Every result carries file:line citations, and every edge is tagged EXTRACTED, INFERRED, or AMBIGUOUS, so the agent knows what was parsed versus guessed.

/graphify .

How the plugin behaves

The plugin is deliberately small and deliberately polite. Before a tool call runs, it checks two things: is this the bash tool, and does graphify-out/graph.json exist? Only when both are true does it prepend a one-time reminder to the command, telling the agent to run graphify query for focused questions instead of grepping raw files. It fires at most once per session and never blocks or rewrites what the agent intended to do.

// .opencode/plugins/graphify.js (excerpt)export const GraphifyPlugin = async ({ directory }) => {  let reminded = false;   return {    "tool.execute.before": async (input, output) => {      if (reminded) return;      if (!existsSync(join(directory, "graphify-out", "graph.json"))) return;       if (input.tool === "bash") {        // prepends a one-time knowledge-graph reminder to the command        reminded = true;      }    },  };};

Two implementation details worth knowing because they were shaped by real bug reports: the reminder text is plain words with no backticks (backticks inside the quoted echo would trigger shell command substitution), and it is joined to the command with ; rather than &&, because Windows PowerShell 5.1 rejects && as a statement separator. OpenCode cannot hard-block a tool call, so there is no strict mode here; blocking exists only on Claude Code.

Keeping the graph current

After edits, graphify update . re-extracts only the files that changed (AST-only, no API cost); the AGENTS.md rules tell the agent to run it after modifying code. graphify hook install adds post-commit and post-checkout git hooks that refresh the graph automatically. The full command set is in the CLI reference.

Troubleshooting

• Graphify installed but OpenCode shows no sign of it: check whether you ran the bare graphify install. It targets Claude Code; run graphify opencode install instead (see the gotcha above).
• No reminder appears before bash commands: expected until graphify-out/graph.json exists, and also after the first bash call of a session, since the reminder is one-shot by design.
• /graphify does nothing: for a project-scoped install, confirm the skill is at .opencode/skills/graphify/SKILL.md and that AGENTS.md has the graphify section, then start a new session.
• Plugin listed twice in opencode.json: harmless but tidy-uppable; the entry uses forward slashes on every platform, and re-running graphify opencode install will not add duplicates.
• graphify: command not foundin OpenCode's shell: the uv or pipx tool bin dir (~/.local/bin) is not on PATH. Run uv tool update-shell (or pipx ensurepath) and restart OpenCode.

OpenCode FAQ

Next steps

The quickstart walks the whole flow from install to first query, and the CLI reference covers every command the rules point OpenCode at. The same graph serves every assistant you run: see Graphify + Codex (the other AGENTS.md platform), Graphify + Claude Code, or browse the full list on the integrations page.