opencode-raven

Hard tool/MCP rerouter for opencode Blocks configured tools and MCPs for non-Raven agents, then routes those requests through a focused Raven agent to avoid flooding and wasting your main model's context, mostly from searches, docs, web pages, GitHub examples, and verbose MCP calls.

Why?

Tool-heavy work floods context. Search, docs, web, GitHub examples, and verbose MCP calls can dump raw results into your expensive main model. Raven is a hard blocker-rerouter: configured tools fail closed for non-Raven agents and must be delegated through raven_seek, where a focused Raven agent performs the work and returns a compact answer.

Raven fixes three problems:

1. Context flooding — Keep noisy tool results out of the main session. Raven summarizes tool/MCP output before returning it.
2. Cost — Use a cheaper model like opencode/deepseek-v4-flash-free for tool-heavy work while saving your main model's context for decisions and edits.
3. Enforcement — This is not soft nudging. Raven blocks configured tools/MCP prefixes for non-Raven agents and gives them the exact raven_seek retry path.

Raven defaults to search/fetch/docs/GitHub routing, but it works with any MCP whose opencode tool names share a prefix.

Important limitation: opencode still loads enabled MCP tool schemas into the main session. Raven saves context from tool calls and raw results, but it cannot hide initial MCP schemas from the main model until opencode supports agent-scoped MCP visibility.

Install

bun add opencode-raven
# or
npm install opencode-raven

Then add to your opencode.jsonc:

{
  "plugin": ["opencode-raven"]
}

Restart opencode.

Commands

Config persists across restarts in ~/.config/opencode/raven-config.json (global, shared across all projects). Auto-created on first run.

Updates

opencode caches npm plugins, so "opencode-raven" / "opencode-raven@latest" may not automatically refresh after a new npm release.

Raven checks npm after the TUI starts. If an update is available, it shows a notification. /raven also shows the current version and update availability. To update:

/raven update

This checks npm, clears Raven's opencode plugin cache when a newer version exists, and tells you to restart opencode.

Manual alternatives:

bun update --latest opencode-raven
# or
npm install opencode-raven@latest

If opencode still loads the old cached plugin, clear the opencode plugin cache and restart:

Remove-Item -Recurse -Force "$HOME\.cache\opencode\packages\opencode-raven*"

rm -rf ~/.cache/opencode/packages/opencode-raven*

Direct access

You can call Raven directly with @Raven in any opencode chat. The Raven agent runs with full filesystem and MCP access — no permission prompts.

raven_seek

When configured tools/MCPs are blocked, agents use raven_seek — a unified delegation tool that sends the request to Raven. It handles routed MCP requests, local codebase search, filesystem discovery, specific URL/page reads, web/docs research, GitHub examples, and command-output/system inspection. Output includes elapsed time and tokens processed.

raven_seek(query: "how to use useEffect cleanup")
raven_seek(query: "Fetch/read https://example.com and summarize install steps")
raven_seek(query: "Check whether archivemount/libarchive supports ISO or UDF. Use docs, web, or command output as needed.")

The main agent doesn't see Raven's internal tool calls or raw tool output — just the final findings. Raven parallelizes independent tool calls internally within a single session.

Configuration

raven-config.json

Located at ~/.config/opencode/raven-config.json. Auto-created on first run and auto-migrated on startup when new config fields are added. Default route lists are only applied when the field is missing, so removed tools/MCP prefixes stay removed. Edit manually or use /raven commands:

{
  "enabled": true,
  "model": "opencode/deepseek-v4-flash-free",
  "reasoning_effort": "low",
  "ravenInstructions": "",
  "routeTools": ["grep", "glob", "webfetch", "fetch", "bash"],
  "routeMcpServers": ["context7", "exa", "grep_app"],
  "allowBundledMCPServers": true,
  "excludeAgents": [],
  "excludeTools": [],
  "timeout": 180
}

MCP servers

All three MCPs work without API keys. Add keys for higher rate limits:

When allowBundledMCPServers is true, Raven auto-registers bundled Context7, Exa, and Grep.app MCP defaults. It merges those MCP defaults with your existing opencode.jsonc settings, preserving custom headers, URLs, and enabled: false overrides. Set allowBundledMCPServers to false if you do not want Raven to add bundled MCP defaults.

To add other MCPs, configure them in opencode.jsonc, then add their server prefix to routeMcpServers if you want Raven to route them. Raven does not install arbitrary MCPs from raven-config.json.

Use ravenInstructions for extra Raven-only guidance, such as how to use custom MCPs:

{
  "ravenInstructions": "For Linear requests, prefer assigned open issues and include issue keys in the answer."
}

To add an API key, override the MCP in your opencode.jsonc with a headers field:

{
  "mcp": {
    "exa": {
      "type": "remote",
      "url": "https://mcp.exa.ai/mcp",
      "headers": { "x-api-key": "{env:EXA_API_KEY}" },
      "enabled": true
    }
  }
}

To disable an MCP entirely:

{
  "mcp": {
    "exa": { "type": "remote", "url": "https://mcp.exa.ai/mcp", "enabled": false }
  }
}

How it works

Routed tools (blocked and redirected except for Raven and any agents in excludeAgents)

By default, Raven routes these built-in tools and MCP server prefixes:

To route another MCP, add its server prefix. For example, "linear" routes every tool named linear_* through Raven:

/raven route mcp add linear

This works for any MCP whose opencode tool names share a prefix. For example, if an MCP exposes tools named my_mcp_search, my_mcp_fetch, and my_mcp_get_item, this routes all of them:

/raven route mcp add my_mcp

The prefix must match the actual tool name before _. If the tools are named project_search, add project, not the display name of the MCP. Matching is case-insensitive.

If an MCP is routed but one tool should remain direct, add the exact tool to excludeTools:

{
  "routeMcpServers": ["context7", "exa", "grep_app", "my_mcp"],
  "excludeTools": ["my_mcp_validate"]
}

To route one specific tool without routing the whole MCP server:

/raven route tool add linear_search_issues

Bash commands — intercepted only while bash is included in routeTools and the command matches a primary search/discovery pattern:

Unrestricted for non-Raven agents: read, task, subtask, raven_seek, non-routed tools, and non-search bash commands.

Allowed output filters: Piped filters like command | grep ..., command | rg ..., command | findstr ..., and command | head ... are allowed. Raven only blocks search commands when they are used as primary discovery commands, not when they filter bounded output from another command.

To stop routing search-like bash commands, remove bash from routeTools:

/raven route tool remove bash

Bash quote stripping: Quoted content in bash commands is stripped before pattern matching — echo "use grep here" won't falsely trigger blocking.

Comment stripping: Shell comments are stripped before matching — # use grep later won't falsely trigger blocking.

Subagent guidance: Every non-Raven, non-excluded subagent gets <raven_guidance> injected into its prompt at spawn time.

The injected guidance includes the current routeTools and routeMcpServers, including user-added custom MCP prefixes, so subagents know which calls must go through raven_seek.

What Raven Saves

Raven saves context from tool call results and raw MCP output by moving the work into a Raven session and returning a compact answer. It does not currently save context from MCP tool schemas that opencode loads into the main session when an MCP is enabled globally.

This means large MCPs may still increase the main session's starting context. Raven still prevents repeated verbose tool outputs from accumulating in the main session.

Agent capabilities

Raven itself has access to these tools (blocked for other agents when configured by the plugin):

raven_seek is denied inside Raven itself so Raven cannot recursively call its own wrapper tool. Raven uses direct tools/MCPs instead.

Raven returns compact findings: answer, sources, relevant details, recommended next step, and uncertainty.

License

MIT