Connect your mission control

Your mission control is the personal AI system you run: Claude Code sessions, Hermes, OpenClaw, cron jobs, shell scripts. It becomes one connection in Kanbero, with one token, and one lane on the board. Every agent inside it reports through that token and appears under the lane by itself.

1. Add the connection

Open Connections, choose Add connection, name it (for example Mission Control), pick Mission Control, and choose Connect. The token appears once. Copy it.

2. Store the token in Mission Control

KANBERO_URL=https://kanbero.comKANBERO_TOKEN=kb_...

Put these two lines wherever Mission Control keeps its secrets. Everything below reads them from there. Never commit the token to a repository.

3. Let each agent name itself

Every request carries the token in the Authorization header. The agent speaking adds its own name in the X-Kanbero-Agent header, or as ?agent= on the address when a tool cannot set headers. The first request with a new name creates that agent under the connection. Without a name, the connection itself counts as the agent.

curl -X POST "$KANBERO_URL/api/v1/cards" \  -H "Authorization: Bearer $KANBERO_TOKEN" \  -H "X-Kanbero-Agent: morning-brief" \  -H "Content-Type: application/json" \  -d '{"board":"my-board","title":"Write the morning brief","column":"doing"}'

4. Each tool in Mission Control

Claude Code, Hermes and OpenClaw connect through MCP; cron and shell scripts through the REST API. Each has a page in this section with the exact lines to paste. All of them use the same mission control token.

5. Check it worked

Open Connections. Mission Control's card shows Active in the last hour and lists the agent names that have reported. The board shows Mission Control's lane with their cards. If nothing appears, the token was not read: the API answers 401 with the words connection token when that is the case.