What is opcode?
opcode provides a desktop interface for developers working with Claude Code. It lets users browse projects, resume coding sessions, create custom agents, and review agent execution history. It is an independent project, not affiliated with or endorsed by Anthropic.
The application includes usage and cost analytics, MCP server configuration, branching session checkpoints, and an editor for CLAUDE.md files. Agents run in separate processes, with configurable file and network permissions. The repository states that application data is stored locally and that opcode collects no telemetry.
opcode is distributed as source code under the AGPL license, with build instructions for Windows, macOS, and Linux. It requires the Claude Code CLI. The supplied documentation says release executables are forthcoming, so deployment should be planned around building the application from source.
Key capabilities
- Session management Browse Claude Code projects, search session history, and resume previous coding sessions.
- Custom agents Define system prompts, select models, configure permissions, and run agents in background processes with execution logs.
- Usage analytics Review token consumption and API costs by model, project, and period, and export usage data.
- MCP management Add server configurations manually or through JSON, import configurations from Claude Desktop, and test connectivity.
- Session checkpoints Create checkpoints, explore a branching timeline, restore earlier states, and inspect differences.
- Project instructions Find and edit CLAUDE.md files with Markdown highlighting and a rendered preview.
Where opcode fits
opcode fits into development workflows that already use Claude Code and need a graphical workspace for navigating sessions, running specialized agents, and reviewing usage. Its checkpoint tools support exploring alternative session paths, while its MCP manager centralizes server configuration.
Before deployment, verify that the Claude Code CLI is available, that the workstation meets the documented build requirements, and that the team can maintain a source-built desktop application. Review agent file and network permissions and the data handling of connected services; local application storage does not establish that model requests remain on the workstation.
Reviews of opcode
Be the first to share your experience with opcode.
Write a review
Loading review form…
