Flight plans for AI-assisted coding
What is Flight Deck?
Agents can plan and execute a task, but breaking down a Very Long Horizon effort largely means drowning in a sea of Markdown files. Flight Deck doesn’t replace Claude Code, Antigravity, or any other agent or its capabilities. Instead, it’s a companion framework for Very Long Horizon Task (VLHT) management and execution. It’s also a hub: multiple agents, sessions, even different contributors like Claude Code and Antigravity can contribute to one plan and understand each other’s work.
Missions and flights
A mission is one Very Long Horizon Task — an effort measured in days, not minutes. Its flights are the scopes it breaks into, and each flight has legs. A mission is engineered never to wait on you mid-run: it drains itself, pausing only at the few points where a human genuinely changes the outcome.
Using it
Start a project with your coding agent the way you normally would, then file a mission with Flight Deck MCP. Your agent breaks it into flights, legs, and waypoints you can review and understand. You clear it for launch once — then it flies, and you watch in real time.
The board
Attention is the scarce resource, so the deck is a router for it. Every mission carries a signal your agent sets — awaiting your reply, holding for a greenlight, parked, or simply flying — and the board sorts by urgency. With three or five runs going at once, it answers the only question that matters: which one needs me next?
Tractability
Each leg is scored not by how big it is, but by how knowable it is: how predictable its blast radius is, how reachable its verification, how tightly its requirements pin down the work. A leg at the bottom of that scale is a hard block — it doesn’t fly until it’s decomposed, given a verification plan, or rescoped. So “review and approve” is a real decision, not a rubber stamp.
The Flight Director
You are the Flight Director. Your one authorization is the mission greenlight: your agent asks for it, the run holds, and nothing fans out until you clear it. After that the run is hands-off by design. If a scope can’t be satisfied, it parks itself and the run moves on to the next one — it surfaces on your board instead of interrupting you for it. Your deck, your call.
Your key
The MCP key you generate is how your agent connects to this deck, by URL, nothing to install. Paste the command into your agent, hand it a project, and watch it fly.
Flight plans for AI-assisted coding
What is Flight Deck?
Agents can plan and execute a task, but breaking down a Very Long Horizon effort largely means drowning in a sea of Markdown files. Flight Deck doesn’t replace Claude Code, Antigravity, or any other agent or its capabilities. Instead, it’s a companion framework for Very Long Horizon Task (VLHT) management and execution. It’s also a hub: multiple agents, sessions, even different contributors like Claude Code and Antigravity can contribute to one plan and understand each other’s work.
Missions and flights
A mission is one Very Long Horizon Task — an effort measured in days, not minutes. Its flights are the scopes it breaks into, and each flight has legs. A mission is engineered never to wait on you mid-run: it drains itself, pausing only at the few points where a human genuinely changes the outcome.
Using it
Start a project with your coding agent the way you normally would, then file a mission with Flight Deck MCP. Your agent breaks it into flights, legs, and waypoints you can review and understand. You clear it for launch once — then it flies, and you watch in real time.
The board
Attention is the scarce resource, so the deck is a router for it. Every mission carries a signal your agent sets — awaiting your reply, holding for a greenlight, parked, or simply flying — and the board sorts by urgency. With three or five runs going at once, it answers the only question that matters: which one needs me next?
Tractability
Each leg is scored not by how big it is, but by how knowable it is: how predictable its blast radius is, how reachable its verification, how tightly its requirements pin down the work. A leg at the bottom of that scale is a hard block — it doesn’t fly until it’s decomposed, given a verification plan, or rescoped. So “review and approve” is a real decision, not a rubber stamp.
The Flight Director
You are the Flight Director. Your one authorization is the mission greenlight: your agent asks for it, the run holds, and nothing fans out until you clear it. After that the run is hands-off by design. If a scope can’t be satisfied, it parks itself and the run moves on to the next one — it surfaces on your board instead of interrupting you for it. Your deck, your call.
Your key
The MCP key you generate is how your agent connects to this deck, by URL, nothing to install. Paste the command into your agent, hand it a project, and watch it fly.