Embedded terminal

Kanban has a terminal that runs Claude Code for a session, in the same place as its task board. Under the hub the terminal is on by default. When you run Kanban alone, it is off.

Use the terminal

In Kanban:

Key	Action
`Ctrl+Alt+N`	Start a new session
`Ctrl+Alt+R`	Resume a past session
`Ctrl+Alt+S`	Swap to the previous session
Ctrl+`	Show or hide the terminal for the selected session
Alt+`	Move focus between the terminal and the page

The terminal process runs on the hub’s machine. When you switch tools, switch sessions, or reload the page, it keeps running. For the full guide, see Embedded terminal in the Kanban docs.

The window asks before it closes

While a terminal is attached, the hub asks before the window closes. In a terminal, Ctrl+W deletes a word, but the browser uses the same key to close the window. The prompt stops a key meant for the terminal from closing the hub.

The terminal token

The terminal can run any command, so it needs its own token. The hub makes a new one each time it starts and gives it to Kanban. You do not type it.

If the hub restarts while the page stays open, Kanban asks the hub for the new token and connects again. You do not have to reload.

Turn the terminal off

Start the hub with --disable-terminal:

npx claude-code-hub --disable-terminal

Or add this to ~/.claude-hub/config.json, then restart the hub:

{
  "terminal": { "enabled": false }
}

The terminal is also off when the hub listens on an address other than loopback, for example with --host 0.0.0.0. Kanban refuses to run it there.