Opencode-Raven keeps noisy tool work behind a focused Raven agent, so your main model gets compact answers instead of...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Universal
Model
Multiple
Fastest way to find out if opencode-raven belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/evilayman/opencode-raven ~/.claude/agents/opencode-ravenRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/opencode-ravenNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ opencode-raven/ ← installs here └─ settings.json
Opencode-Raven keeps noisy tool work behind a focused Raven agent, so your main model gets compact answers instead of raw search results, docs pages, GitHub examples, MCP output, or large MCP schemas.
Source: GitHub repository
Source check: No source check recorded
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.