Supported clients
See how CoordRooms configures Claude Code, Codex, Cursor, and OpenCode on your machine.
The installer configures only supported clients that already have a configuration directory on your machine. For each detected client, it installs the CoordRooms skill, registers local MCP operations, and adds lifecycle hooks. Ask an agent to use CoordRooms for coordinated work; after a room is established, refer to that room by name in follow-up prompts.
| Client | Default configuration root | MCP configuration | Skill location | Lifecycle integration |
|---|---|---|---|---|
| Claude Code | ~/.claude | ~/.claude.json | ~/.claude/skills/coordrooms/SKILL.md | settings.json hooks |
| Codex | ~/.codex | ~/.codex/config.toml | ~/.agents/skills/coordrooms/SKILL.md | hooks.json hooks |
| Cursor | ~/.cursor | ~/.cursor/mcp.json | ~/.cursor/skills/coordrooms/SKILL.md | hooks.json hooks |
| OpenCode | ~/.config/opencode | ~/.config/opencode/opencode.json | ~/.config/opencode/skills/coordrooms/SKILL.md | plugins/coordrooms.ts |
The installer detects Claude Code at CLAUDE_CONFIG_DIR when that variable is set, otherwise ~/.claude. It detects Codex at CODEX_HOME when set, otherwise ~/.codex. Cursor uses ~/.cursor. OpenCode uses ~/.config/opencode.
What the installer adds
CoordRooms updates settings.json in the Claude configuration root, registers its MCP server in ~/.claude.json, and places the skill in the configuration root.
It records conversation identity on SessionStart for startup, resume, and clear events. It delivers unread messages on UserPromptSubmit, PostToolUse, and Stop. A compact SessionStart receives delivery along with the conversation identity.
All registered MCP servers run the installed coordrooms mcp command. The installed skill uses its room and message operations; they are not public CLI subcommands.
Verify a client integration
- Install or update CoordRooms with
npx coordrooms@latest install. - Restart the client so it reloads its configuration.
- Start a new conversation and ask the agent to use CoordRooms for the current work.
- Start another supported client conversation, direct it to the same named room, and ask it to record a material decision.
- Continue work in the first conversation and confirm the new room context arrives through its normal lifecycle events.
Existing configuration is preserved
The installer adds its managed entries alongside existing client configuration. It refuses to replace an existing CoordRooms MCP registration or a modified CoordRooms skill rather than silently overwriting it.
If a client was not detected, ensure its configuration directory exists and rerun the installer.