Skip to main content

​
Headless

BossMode is headless-first. That means every action you can take in the dashboard, you can also take from:
  • A terminal (the CLI — @bossmode/cli)
  • An agent’s tool surface (the MCP server — @bossmode/mcp-server)
  • A plain HTTP call (the REST API — /api/pro/*)
All three talk to the same Convex-authoritative core. Signing up once gives you access to all three.

​
Why headless

The end-user of BossMode is often an AI agent, not a human. Salesforce announced the same architecture shift at TDX 2026 (“Headless 360”). BossMode shipped with that model from day zero. Practical implications:
  • Your agents never log into a web dashboard. They hit the MCP tool surface or the REST API directly.
  • Your CI pipelines can manage workspaces. Install packs, run directives, pull reports — all scriptable.
  • Multi-tenant by default. One MCP server, many client workspaces, role-scoped tokens per tenant.

​
Which surface should I use?

You want to…Use
Give a directive from the terminalCLI
Expose BossMode tools to Claude Code / Cursor / ContinueMCP
Wire BossMode into a Node/Python pipelineREST API
Receive real-time events from BossModeWebhooks

​
Quickstart

Sign up at bossmode.ing/signup, then install the CLI: 
npx @bossmode/cli@latest init --wizard
That one command pairs your device, registers it with your workspace, and spawns the local daemon. You’re headless-ready.

​
Next steps

CLI

Install and use the bossmode CLI to control your workspace from the terminal or CI.

MCP Server

Wire BossMode tools directly into Claude Desktop, Claude Code, Cursor, or Continue.

REST API

Drive BossMode programmatically from any HTTP client or your own agent framework.

Webhooks

React to inbound AvatarCzar events and configure outbound webhook destinations.