Skip to main content
🚧 Expanding soon — full Claude Code integration documentation is in progress.

​
BossMode in Claude Code

BossMode integrates with Claude Code via the BossMode skill. The skill gives Claude Code access to your full operational context, standing orders, and directive API — all from inside a coding session.

​
The BossMode skill

The bossmode-consigliere skill is available in Claude Code. It wraps the BossMode API with Claude-native commands: 
bossmode:get-context
Returns your full operational context — signals, packets, standing orders, approvals, metrics, Guardian state, and buyer context. 
bossmode:directive "<instruction>" --capo <role>
Issues a directive to the consigliere. 
bossmode:approvals
Lists pending approval queue items. 
bossmode:kill-switch "<reason>"
Activates the kill switch.

​
Setup

Ensure BOSSMODE_API_TOKEN is in your environment: 
export BOSSMODE_API_TOKEN=bm_live_your_token
The skill reads the token automatically.

​
MCP server alternative

If you prefer explicit MCP configuration, install the MCP server: 
npm i -g @acelabs/bossmode-mcp-server
Add to your MCP config (.mcp.json or Claude Code settings): 
{
  "mcpServers": {
    "bossmode": {
      "command": "bossmode-mcp-server",
      "env": {
        "BOSSMODE_API_TOKEN": "bm_live_your_token"
      }
    }
  }
}

​
Example workflow

In a Claude Code session: 
> bossmode:get-context

[BossMode returns full context]

Now review the standing orders. Draft a follow-up email for the cold lead segment that's been 
dormant for 14 days. Match the voice in buyer profile 1. Queue for approval.

> bossmode:directive "Draft re-engagement email for 14-day dormant cold leads" --capo capo_marketing
Claude Code drafts the email using BossMode context, queues it for approval, and logs the move.

​
Requirements

  • Claude Code with skill support
  • BossMode Pro account
  • BOSSMODE_API_TOKEN environment variable