Documentation Index
Fetch the complete documentation index at: https://docs.getmonocle.sh/llms.txt
Use this file to discover all available pages before exploring further.
monocle connects to your agent through one of two integration modes: MCP tools or skills. Run monocle register to configure the connection.
- MCP tools mode configures an MCP server that exposes monocle’s review operations as tools the agent can call directly. This is the default for Claude Code.
- Skills mode installs skill files — small instruction files that tell the agent which CLI commands to run. This is the default for all other agents.
Register monocle with your agent
monocle register # interactive picker
monocle register claude # or: opencode, codex, gemini, all
--global to install at the user level instead of the current project:
monocle register claude --global
--integration-mode:
monocle register claude --integration-mode skills # force skills mode
monocle register opencode --integration-mode mcp # force MCP tools mode
Set up each agent
Claude Code
OpenCode
Codex CLI
Gemini CLI
All agents
Other agents
Register via CLI
By default, this configures an MCP server in .mcp.json that exposes monocle’s review tools directly, and installs slash commands in .claude/commands/. Claude Code calls the MCP tools (review_status, get_feedback, send_artifact, add_files) instead of running CLI commands.To use skills mode instead (the previous default), pass --integration-mode skills:monocle register claude --integration-mode skills
Enable push notifications
Claude Code supports MCP channels, which deliver your review feedback directly into the agent’s context the moment you submit — no polling needed. Start Claude Code with the channel flag to enable this:claude --dangerously-load-development-channels plugin:monocle@monocle
If you start or restart monocle while Claude Code is already running, the MCP channel may need to reconnect. Type /mcp in Claude Code and select monocle to reconnect.
Register via CLI
monocle register opencode
.opencode/skills/. OpenCode uses pull-based feedback — the agent retrieves your reviews by running the /get-feedback skill.Register via CLI
This installs skills into .codex/skills/. Codex uses pull-based feedback — the agent retrieves your reviews by running the /get-feedback skill.Register via CLI
This installs skills into .gemini/skills/. Gemini CLI uses pull-based feedback — the agent retrieves your reviews by running the /get-feedback skill.Register monocle for every supported agent at once:Use --global to install at the user level:monocle register all --global
If your agent isn’t listed above, you can set up monocle manually using either MCP tools or skills.If your agent supports MCP servers via stdio, point it at monocle’s built-in MCP server:This exposes the review_status, get_feedback, send_artifact, and add_files tools over stdio. Add this as an MCP server in your agent’s config, the same way you would any other stdio-based MCP server.Skills
Download the skills.tar.gz archive from the latest release and extract the skill files into wherever your agent expects its skills:curl -Lo skills.tar.gz https://github.com/josephschmitt/monocle/releases/latest/download/skills.tar.gz
tar xzf skills.tar.gz -C /path/to/your/agent/skills/
SKILL.md files that instruct the agent to run monocle review CLI commands for sending artifacts, retrieving feedback, and checking review status. Verify the connection
Start monocle in a terminal alongside your agent:
Press I in the TUI to see the socket path and confirm your agent is connected.