What’s new

Introducing Flightdeck

A coding agent leaves you with the same problem every time: three or four of them are running, each one goes quiet for minutes, and you find out which one needs you by clicking through tabs. That is the whole job Flightdeck removes. It puts every terminal and agent chat on a machine into one resizable wall of tiles, and each tile says out loud whether it is working, done, or waiting on you.

What it does

• Terminals and chats, together. Any tile can hold a terminal or an agent chat, so a build log and the agent that triggered it sit next to each other instead of two clicks apart.
• Split however you think. Split a tile right with ⌘K or down with ⇧⌘K, drag the dividers to any size, move focus with ⌃⌘←→, and expand a single tile to full width when it needs your whole attention.
• A status on every tile. Each one carries a live chip: working, needs input, done, idle, or error. While Flightdeck is open the top bar sums them up, so you can read the state of the whole machine without reading any of it in detail.
• It finds you when it is blocked. The Flightdeck button in the sidebar badges the number of tiles waiting on an answer, and it keeps that badge while Flightdeck is closed. A tile blocked on you is worth surfacing whether or not you happen to be looking at it.
• Your layout stays put. The arrangement is remembered per connection, so reopening a machine brings back the wall you left, not a blank one.

How to open it

The Flightdeck button at the bottom of the activity bar, on the left edge of the workspace. esc closes it and returns you to the editor with everything still running. Connect a machine if you do not have one paired yet.