The manual
Short guides in reading order: install and verify the app, spawn your first session, then drive the grid: twelve cells to a deck, sixty sessions in all. Written against what the app does today.
Set up
Get the app on your computer and spawn the first session.
Install What Helmsman needs on macOS, and how the app lands there. Windows and Linux are coming soon. Verify your download Check your download's checksum yourself, and the signature and notarization on macOS. First run Choose your agent, open a project, and start a task in a live terminal. Agent support What Claude Code and Codex support in Helmsman, and where native terminal controls still apply.
Drive the grid
The daily loop: twelve cells, one window, your attention.
The session grid Up to twelve live sessions per deck, sixty in all. Four across and three down, all on screen at once. Focus and steer The working rhythm: scan the grid, focus the cell that needs you, steer, step back. Keyboard shortcuts Move between cells without the mouse. What is locked today and what lands at launch.
When stuck
Fast answers when a cell misbehaves.
Go deeper
Wider context: the ways to run many sessions, compared.
Ways to run multiple Claude Code sessions Terminal tabs, tmux, git worktrees, VS Code, and dedicated apps, compared honestly for running several Claude Code sessions. Supervise parallel coding agents A working method for watching many Claude Code sessions at once: scan for the cell that needs you, steer it, step back. Parallel Claude Code with git worktrees How to give each Claude Code session its own working copy with git worktrees, and what worktrees do not isolate.
Reference
The words Helmsman uses, defined.
Not answered here? Email hello@helmsman.sh, or see what changed in the changelog.