Using Nautelle
Board
Cards, columns, Ready and Waiting, Auto-run, bulk actions and Discuss mode.
The Board is a project's own work board. A card is a piece of work that Nautelle stores and numbers C-<n> per project, and Run starts a dedicated Claude worker for it. Open it from Project → Board. Cards are not GitHub issues and the orchestrator never dispatches them. See Fleet and live pane for that lane.


Columns
| Column | What it holds |
|---|---|
| Inbox | Suggestions captured from your own Claude Code sessions, waiting for you to accept or dismiss them. Only appears when capture is on |
| To Do | Accepted cards that have not started |
| In progress | A card with an active round |
| Finished | The worker is done, the pull request exists. Waits for CI, an auto-merge or your Accept |
| Completed | Accepted. The worker is closed and its worktree removed |
One rule decides every move, in the API and in the browser. A drag never starts a worker. An active round holds a card in In progress. Automation never moves a card to Completed: only a person does, and Accept never merges unless you pick that option. On a phone, where drag does not work, Move opens a column picker.
Run, feedback and accept
Run starts the card's worker: its own git worktree, its own tmux session and an interactive Claude Code session. Each Run or feedback is a card round. Send feedback to resume the same session as a new round, or message a running session. When the round ends the card goes to Finished and the pull request leaves draft. See Shipping.
Accept moves the card to Completed. The dialog offers to merge the pull request, or to accept without merging, and to delete the branch.
Dependencies, Ready and Waiting
A card can depend on other cards. A To Do card with dependencies shows Ready once every card it depends on is Completed, and Waiting with the open ones listed otherwise. Run still works on a waiting card and only warns you.
Switch on Auto-run when ready and the Run starts by itself when the last dependency is accepted. It starts exactly once, respects the project's slots and budget, and is recorded in the card's activity as an automatic start. Stack stages are ordinary dependencies, so this works for stacks too.
Bulk actions
Tick the checkbox on a card, Cmd or Ctrl+click, or Shift+click for a range in a column. A bar appears with Move to Completed, Move to To Do, Mark finished and Delete, each showing how many of the selection it applies. Cards the move rules refuse are skipped, not failed, and the toast says why. Completing in bulk never merges or closes a pull request.
Discuss mode
Discuss asks the planning model a question about the project without making a card: how something works, or a review with one of the installed skills. It runs read-only on the runner, has no round limit, and ends when you discard it. Each proposal in a reply has Make a card, which opens New work with the text filled in. Open discussions sit in the Drafts strip.
Fleet work on the Board
Work from the orchestrator's slots and from your own terminal sessions is mirrored onto the Board, so one board shows everything in flight. Mirrored items follow their own source: you cannot drag a fleet slot to another column.