Gimbal View
DirectionDelivery statusFeature inventoryDelivery evidenceQuickstartConsoleWriting workflowsSecrets & orchestrationPrimitivesWorkflow rolesBuilt-in workflowsHarnessesAbout

Feature

Console

A live map of a multi-agent run, served by a Gimbal instance. Watch it, read any part of it, and reach in.

a recorded implementation run
The current console map with a coding turn selected and its recorded result on the right.
A recorded implementation run. The coding turn is selected; its result and model summary are on the right.

The local Gimbal server serves the console and keeps each run’s record on disk. Open the project in the browser to watch a live run or inspect one that has ended.

The map

The map is the workflow’s shape plus the run’s status. Steps stack on one spine in source order. A group’s branches sit side by side between a fork and a join. A loop’s body returns to its planner by an arrow. Each scope is a sheet, so nesting is visible at a glance, and a scope folds when you do not need its inside.

The shape comes from your source, not from the run. go generate reads the workflow function into a typed graph, so the console draws the whole map before the first turn starts, and steps that have not run yet are already there.

The October 8 product assessment observed the map on a small completed review. It did not establish the legibility of a complex live run. That review also found a completed User activity card still labelled “Running.”

The detail pane

The map carries shape and status only. Select an item to inspect its detail; a running turn may open in the Focus tab:

  • A turn: its assignment, the context it was sent, each model call with token counts, and its transcript and tool activity.
  • A scope: the values written in it, including captured command output.
  • A watcher: the supervisor’s instruction, its role, and the source line that attached it.
a watcher, selected
A watcher selected in the current console, showing its role, adapter, and model.
A watcher selected on the map, with its recorded role and model visible.

Reaching into a run

  • Steer a running agent turn with a message. It lands in the live turn, not the next one.
  • Message a loop’s planner. The message waits for the planner’s next decision.
  • Answer an interview. When a workflow calls Interview, the run blocks and the question appears in the console.
  • Stop a turn or cancel the run. They are different actions, and the console says which you are about to do.

A recorded run offers none of these. It is a record.

The runs list

127.0.0.1:8080
The runs list.

Current work first, then everything recorded for the project, with filters for active, needs answer, ended, failed, and cancelled. Each run shows its latest activity and instruction, total cost, elapsed time, sessions, and turns. Runs are tables on disk; opening an old one reads its record, and nothing is replayed.

The recorded review card showed “Completed” without the review finding; the finding was readable after selecting the Result inspector. Do not use the list status alone as a verdict on the requested outcome.

Project conversations

The console can keep a project conversation with a selected Codex, Claude, or Antigravity agent. Each conversation has its own Git branch and worktree. The agent can start a built-in workflow run from that worktree, and the conversation links to its status and run page. The current composer and responses are text-based. Native-session resume after a Gimbal restart is implemented for Codex; this page does not claim equivalent behavior for every harness or a fresh live resume check. The run’s event history and the conversation are separate records.

The same thing from a terminal

gimbal runs                                    # runs in progress
gimbal watch RUN                               # JSON snapshot, then changes
gimbal steer RUN "message" --session ID        # steer an agent turn
gimbal steer RUN "message" --loop SCOPE        # queue a message for a planner
Next Writing workflows