Skip to content
Manual
PDF in preparation

FlowForge Manual

CHAPTER 09 EN

The Cockpit — A Complete Reference

Every screen, every pane, and every keyboard shortcut of the FlowForge terminal cockpit — including talking to ACE by voice from any screen.

The Cockpit — A Complete Reference

Chapter 7 introduced the cockpit as a place you sit. This chapter is the reference: every screen it can show, every pane on those screens, and every keyboard shortcut — including the one that lets you talk to ACE out loud from anywhere in the product.

Launch it from any FlowForge project:

Terminal window
flowforge tui

The cockpit is a full-screen terminal application — FlowForge’s flagship surface. You never leave it to do the day’s work: you spawn workers, watch them run, read and ratify documents, merge pull requests, check your billing, and talk to ACE, all from the same screen.

The cockpit's main screen — the live worker floor, the ACE rail on the right, and the always-visible footer strip of screen shortcuts along the bottom.


How the cockpit is organized

The cockpit is one window that swaps its main screen between a handful of views, with two things that are always present:

  • The ACE rail — a dockable conversation with ACE, the controller. It is always one double-tap of Ctrl away, on every screen.
  • The footer strip — a live row of the highest-priority screen shortcuts, so you never have to remember where you are or where you can go. Press ? for the complete catalogue.

Every status in the cockpit is co-rendered: color is never the only signal. Each state carries a color and a glyph and a label, palettes are chosen to stay legible for color-vision-deficient users, and NO_COLOR is honored. Good terminal craft is part of the product, not an afterthought.


The screens

Each of these is one keystroke away from the main screen. The letter in the margin is the shortcut; the full shortcut tables are below.

KeyScreenWhat it’s for
fFleetThe live worker floor — every running worker, its state, its per-worker context and token telemetry, and the day’s merged-PR ledger.
kKanbanThe ticket board: To-do → In-progress → Done, with live worker cards moving across it.
sStart a FeatureThe Loop-2 blueprint play — describe a feature in words, FlowForge plans it (see Chapter 7).
pForgePlayLaunch a guided play and watch the ceremony chain advance.
wWave controlStart, pace, and stop the automated sprint — the wave that drives a milestone’s tickets to merge (see below).
PStatsThe proof-of-work pride card — your shipped work, at a glance.
bBillingThe billing vitrine — time, cost, and the receipts that prove the work.
dDocsThe customer-doc tree — browse the project’s rendered documents.
vDoc viewerThe Markdown reader for a single document.
hHarmonyRead and ratify design blueprints in-cockpit.
lLog drawerThe live log stream (a ◆ marks new logs).
RRelease NotesEvery version, newest first.
HHook InventoryRead-only: every hook, where it lives, its rule and class.
MManualOpen this manual — the live web edition at flowforgesoft.com/manual/ — in your browser. Always the current version, never a stale local copy.
SSettingsTheme picker (applies live) and the tunable dials — see Chapter 11.

This manual is one keystroke away. Press M anywhere in the cockpit to open the live web edition of this manual in your browser — the same page you’re reading now, always up to date. Inside the desktop app it’s also under Help ▸ FlowForge Manual. The book teaches the key that opens it.

The Fleet view — live workers with per-worker state, context-window and token telemetry, and the merged-PR ledger for the day.

The Kanban board — tickets moving To-do → In-progress → Done, live worker cards included, each co-rendering status by color, glyph, and label.

Waves — the automated sprint

A wave fires a batch of tickets in parallel and auto-drives each one to merge — the fastest way to clear a milestone. FlowForge emits a milestone’s tickets in dependency order, then runs them wave by wave: the current wave’s workers all go at once, and the next wave unlocks only once the one before it has fully merged. A single band in the cockpit shows the live progress — a subtle done-% that climbs as tickets merge and turns green only when the whole plan is complete.

Press w anywhere to open wave control. There you can start the run, fire just the next wave (one step at a time), and stop it — the header states the current wave state (running · queued · done-%) so you always know where you are. Stopping is immediate and safe: the wave already in motion finishes cleanly and no new wave fires, so you can start another whenever you’re ready.


The shortcuts — the complete keymap

These are FlowForge’s global keybindings, grouped exactly as the cockpit’s own help overlay groups them. This table is the single source of truth — the cockpit generates its help screen from the same registry, so what you see here is what the product does. Press ? at any time to bring up the live version.

KeyAction
TabCycle focus forward between panels
Shift+TabCycle focus backward
Ctrl+POpen the Project Switcher
EscReturn to the Project Switcher
?Toggle the help screen
q / Ctrl+CQuit (with confirmation)

Worker lifecycle

KeyAction
nSpawn a new worker on a ticket
KKill the focused worker (with confirmation)
TOpen a terminal — a standalone tmux session (detach with Ctrl-b d)
XRetry brief-injection for a worker whose brief is missing
xDismiss the focused errored (✗) worker row
uUn-archive: restore the focused terminal worker row
AArchive a worker
CClear a worker (terminal rows only, with confirm)
Ctrl+GRe-derive worker status from GitHub (self-heal a mislabel, close a merged ticket)
!Jump straight to the worker that needs you

Screens (open a surface)

KeyAction
sStart a Feature (Loop-2 blueprint play)
fOpen the Fleet view
kOpen the ticket-Kanban board
pOpen ForgePlay
wOpen wave control — start, fire one wave, or stop the automated sprint
POpen the Stats screen
bOpen the Billing vitrine
dOpen the customer-doc tree
vOpen the Markdown doc viewer
hOpen Harmony (read + ratify design blueprints)
l / LOpen the log drawer
ROn the ACE rail: refresh ACE. Elsewhere: open the Release Notes timeline
HOn the ACE rail: handoff (save where we are). Elsewhere: open the Hook Inventory
MOpen this manual — the live web edition — in your browser (the key you just read about)
SOpen Settings (live theme picker + dials)

Merge & tickets

KeyAction
mMerge the selected PR (runs the CI / GOLDEN / confirm gates)
BExplain why the selected ticket is blocked

Context & chrome

KeyAction
Ctrl+TToggle the context-window widget (compact / expanded)
,Open Billing Settings
NOpen “What’s New” (release notes for an available update)
DRetry the docs daemon (when ⚠ DOCS OFFLINE shows)

Every key here is real. The cockpit’s help catalogue is generated from the same keybind registry that wires these keys — a key can never be documented but dead, or wired but undocumented. If a key works, it’s in the help screen; if it’s in the help screen, it works.


Talking to ACE — voice from any screen

Voice is a first-class affordance, not a novelty. You can talk to ACE from any screen — you do not have to be on the ACE rail, and you do not have to stop what you’re doing.

  • Double-tap Ctrl (or press Ctrl+L) — push-to-talk. Speak your request to ACE from anywhere in the cockpit. It degrades gracefully to typing if voice isn’t set up.
  • Alt+V — a legacy alias for the same push-to-talk (also degrades to typing).

Enable voice once:

Terminal window
flowforge voice setup

The push-to-talk affordance — the voice overlay that appears when you double-tap Ctrl to speak to ACE, shown over the main cockpit.

Voice controls

KeyAction
Ctrl·Ctrl / Ctrl+LTalk to ACE from any screen (push-to-talk)
Alt+VTalk to ACE — legacy alias (degrades to typing)
Alt+MMute / unmute ACE’s voice (persistent)
Alt+SToggle SpeakReplies — ACE speaks every reply aloud (persistent)
Alt+IInstall voice support (download the speech models)
Ctrl+YCopy ACE’s last reply to the clipboard
Ctrl+STerminal select — drag-select & copy any conversation text (works mid-compose; your draft is kept)
Ctrl+Shift+VPaste the clipboard into the focused field

The voice pause window — how long ACE waits through a pause before deciding you’re done speaking — is itself tunable in Settings (see Chapter 11), because thinking out loud shouldn’t cut you off.

Being able to say what you want, from any screen, is a feature people would subscribe for on its own. It is the most direct expression of Never Alone: ACE is always one keystroke — or one spoken sentence — away.


Why it matters

The cockpit is where FlowForge’s discipline stops being a set of rules and becomes a place you work. Everything is one keystroke away, every status tells you the truth in more than one way, and ACE is always listening. You don’t manage the workflow — you sit in it.