Clubhouse Mode
Define your instructions, skills, and tools once. Clubhouse materializes the right config for each agent, each orchestrator, every time they wake.
Your project defines the baseline — instructions, permissions, MCP servers, and skills that every agent inherits. Write it once, in one place.
Agents layer their own persona and overrides on top of the shared base. What's unique to an agent stays with the agent. What's shared stays shared.
On wake, Clubhouse assembles the right config for each agent — dynamic placeholders like @@AgentName and @@Path resolve to real values, conditional blocks like @@If(github)...@@EndIf include only what applies.
Switch orchestrators per agent — or run all three in the same project. Clubhouse handles the format differences automatically.
.claude/CLAUDE.md .github/copilot-instructions.md .codex/AGENTS.md .mcp.json .github/mcp.json .codex/config.toml Clubhouse Mode isn't applied once at setup. Each time a durable agent wakes, its config is freshly materialized from the current project defaults — so when shared instructions change, every agent gets the update automatically.
When an agent's config drifts from what Clubhouse Mode would produce, a dialog surfaces on next wake with three options:
Writes your changes back to project defaults with wildcards restored. Every agent benefits.
Locks this agent to its own config, opt-out of shared defaults. Other agents are unaffected.
Restores from shared defaults, discards the local diff. Clean slate from the project config.
You are @@AgentName, a specialized agent working in @@Path.
@@If(github)
When creating pull requests, use the GitHub CLI: gh pr create
@@EndIf
Build: @@BuildCommand
Test: @@TestCommand
Project-level instructions. The @@variables resolve differently for each agent at wake time.
Download Clubhouse and set up your first project config. One source of truth for every agent on your team.