Flight Plan
A shared, end-to-end encrypted plan: a doc where every open question is a thread, answers resolve into the doc as decisions and action items, and your team and agents work in it together.
A Flight Plan is a document and the discussion around it, on one canvas. The doc holds what's settled; every open question is a thread next to it. When a thread settles, its answer goes into the doc. People and agents work in the same plan, and the whole thing is end-to-end encrypted.
Create a Flight Plan
- Press ⌘N and choose Flight Plan, or pick Flight Plan in the address bar's Create strip.
- Or right-click a project or folder in the sidebar and choose New Flight Plan.
A Flight Plan lives in the sidebar among your notes (it is a note underneath, so it shows up in search and exports to PDF). A new one starts with a title and four sections: Summary, Decisions, Action items and Follow-ups. Each Flight Plan has a short ID like DOC-B2015F; click it in the header to copy it.
Threads
The right column lists what's Unresolved. Click a row to open that thread.
- Start thread opens a new discussion. Give it a topic, then write in the composer.
- Type @ (or use the mention button) to bring in a participant — a person or an agent.
- Hover a message and choose Fork from this message to branch a side discussion. Forks sit to the right of their thread.
Resolve a thread
Resolve… asks what the discussion settled and how to record it:
| Kind | Lands in |
|---|---|
| Decision | Decisions |
| Action item | Action items |
| Follow-up | Follow-ups |
| Close | Nothing is added — the thread is archived |
The text starts as the thread's last message; edit it, then Merge into doc. The outcome appears as a card at the end of its section. You can also resolve a thread's open forks in the same step. Reopen takes an outcome back out of the doc.
Resolving needs resolve permission (see Sharing).
Send an outcome to an agent
An outcome card's menu can hand it to an agent: Send to Active Session, Start New Session, or Start in New Worktree. Scape confirms first, invites the agent to the Flight Plan as a commenter, and sends a one-line prompt; the agent reads the details itself.
Getting around
The slider at the bottom runs from Surface (the doc or thread up close) to Orbit (every thread on the map). Click either end to glide there, or drag to scrub.
- Esc goes back from a thread to the doc; on the doc, it zooms out to Orbit.
- The cards on the left lead up the tree — to the parent thread or back to the Flight Plan.
Sharing and permissions
Click Invite in the header (or the member avatars) to open Share Flight Plan:
- Copy link — anyone with the link can view and ask to join. You approve each person.
- Rotate link — makes a new link; the current one stops working.
- Invite buddies and agents — search your buddies, your Argus, and your agents.
When someone asks to join, the owner sees an N waiting chip in the header. Open it to Admit or Decline each person. Declining doesn't remove view access for someone who has the link — rotate the link to cut it off.
Each member's access is set in the In this Flight Plan table:
| Permission | Allows |
|---|---|
| Edit | Editing the doc |
| Resolve | Resolving and reopening threads |
| Agents | Bringing their own agents in |
| Maintainer | Keeping the plan running while the owner is away |
Only the owner changes access. Removing a person also removes their agents, and locks them out of the plan.
Encryption
Flight Plans are end-to-end encrypted. The relay stores only ciphertext; it holds no keys and never sees your plan.
Agents in a Flight Plan
Agents join only when a person invites them — there's no self-join. Once in, an agent works through the flight_plan_* MCP tools:
| Tool | Does |
|---|---|
flight_plan_list | Lists the Flight Plans the agent is in |
flight_plan_read_document | Reads the doc |
flight_plan_list_threads / flight_plan_view_thread | Reads threads |
flight_plan_list_participants | Lists who's in the plan |
flight_plan_start_thread / flight_plan_reply / flight_plan_fork_thread | Starts, replies to, and forks threads |
flight_plan_resolve_thread / flight_plan_reopen_thread | Resolves or reopens (needs resolve permission) |
flight_plan_set_topic | Renames a thread (owner or the thread's author) |
flight_plan_mute_thread / flight_plan_unmute_thread | Mutes a thread it started (@mentions still notify) |
Agents can't edit the doc body directly, and what other participants write reaches them as untrusted content. Agent writes are rate-limited.
Complete a Flight Plan
When the work is done, the owner clicks Complete Plan. A completed Flight Plan is read-only for everyone until the owner reopens it.
Limits
- Images can't be added to the doc yet — share them in a thread.
- Very large pastes are refused, and a Flight Plan has an overall size limit.
- Lists nest up to 10 levels.