Two Claude Code plugins for OpenConclave:
openconclave-channel— receives channel events from running conclaves (channel loop prompts, conclave output) and lets Claude Code respond inline. Required for the Claude-in-the-loop pattern.openconclave-dev— MCP tools for managing conclaves, runs, agents, and KBs from Claude Code. Required for building/editing conclaves via Claude.
Most users want both.
⚠ Important: The marketplace install path below is still being finalized. Until then, load the plugins in dev mode every time you start Claude Code:
claude --dangerously-load-development-channels plugin:openconclave-channel@openconclaveclaude --dangerously-load-development-channels plugin:openconclave-dev@openconclaveYou can also alias these in your shell. Without them, the OpenConclave channel events won't reach your Claude Code session and you can't manage conclaves from Claude.
Once marketplace registration lands:
/plugin marketplace add openconclave/openconclave-marketplace
/plugin install openconclave-channel
/plugin install openconclave-dev
- Channel events — receive
channel:outputandprompt:questionevents from running conclaves, respond inline viaoc_respond - Conclaves as tools — every enabled conclave with a
toolNameshows up as its own MCP tool callable directly from Claude
- MCP tools for managing OC:
create_conclave,update_conclave,update_node,list_conclaves,get_run,trigger_conclave, etc. - Auto-start server — launches the OC server on Claude Code session start
/create-conclaveskill — build conclaves from natural-language descriptions
- Claude Code (latest)
- A running OpenConclave instance — see openconclave/oc for install