Kanban Code
Connect the Kanban Code server on your machine through an outbound relay so your personal agents can start and follow tasks there.
Connect the Kanban Code server that runs on your own machine, so your personal agents in Laze, hosted ones too, can start Kanban Code tasks there and follow them.
Laze never dials your machine. The laze connect service on it opens an outbound connection to Laze (a relay) and answers on its behalf. Nothing needs to be opened to the internet.
Connect it
- On the machine that runs Kanban Code, pair a device with the agent scope. It prints a device token once.
kanban remote pair --name laze --scope agent --jsonOn a box, use kanban-code-server pair laze --scope agent instead.
- Sign the Laze CLI in as yourself with
laze login, then pipe the token in.
kanban remote pair --name laze --scope agent --json | jq -r .token | laze kanban connectOptions: --url (default http://127.0.0.1:7780), --label, --name (default kanban) and --sensitivity auto|checked|ask|human_only (default auto).
- Check the relay.
laze kanban statusIt says connected once Laze lists the tools. The server also appears on the Connectors page with its tools.
Tools your agents get
The tools reach your agents through the MCP gateway.
| Tool | What it does |
|---|---|
kanban__task_create | Creates a card and starts it. Takes a project and a prompt, and optionally a name, a worktree and a machine. |
kanban__card_status | Returns the column, whether the card is busy, queued prompts, the branch and pull requests. |
kanban__card_reply | Returns the card's last reply and whether it is still working. |
kanban__card_prompt | Sends a follow-up prompt, delivered when the current turn ends, or now. |
Who can use it
The connection lives in your own keychain, so only your personal agents reach it, and only in turns you started. When a teammate asks your agent, Laze asks you.
Every call is a vault use with the connection's level, which is Auto by default. Raise the connection, or single tools such as task_create, to Ask on the Connectors page to approve each call. Every call is in the vault audit.
Security
The device token is kept in the Laze vault as the connection's header, never on your machine. Laze sends it with each allowed call through the relay. The relay key in the laze connect folder only lets the relay hold its connection.
Use a device with the agent scope: it cannot open terminals.
To cut access, revoke the device in Kanban Code or remove the connection in Laze. Running laze kanban connect again gives the relay a new key and replaces the token.
kanban remote revoke laze