Work in Flight (the worktree ledger and its Saved Work vault)

What it is

Work in Flight and its Saved Work vault are the reader-facing half of the worktree ledger — the record Omniscio keeps of every git workspace it has made, who owns it, and what it is for.

• The Work in Flight strip turns that record into plain language: a hub filter (one pill per repo, busiest first), a headline of how many workspaces need attention, a chip per non-empty state, and one row per workspace that wants a person — each with the work's title and a Keep button.
• The Saved Work vault makes the repository's rescue refs and its branch archives visible and restorable, so a non-technical operator can see that nothing is thrown away.
• A ledger activity readout compares the record with git — how many rows are behind, ahead, or otherwise out of step — so the index's own health is visible.

Where to find it

It lives inside the Dev Pipeline panel — a built-in sidebar panel — on its Live view, in between the runs and the worktree list. When nothing is running the panel shows its empty state instead, and none of Work in Flight appears.

It is an in-development feature: it is off by default and revealed by its own Settings → Lab toggle, "Work in Flight (Worktree Ledger)". Until that switch is on, the panel shows none of it.

How it behaves

• Six plain-language states. A workspace is needs you, stuck, being built, landing, kept, or done, and the chips summarise the counts ("3 need you", "5 being built").
• "N need attention" is counted by the app, not the screen. The number is worked out in the background — the selected hub's count when a hub is picked, the overall count otherwise — so the headline stays right even when a busy repo's long finished list is capped for display.
• Keep protects a workspace. Pressing Keep on a row pins it so the cleanup jobs leave it alone. Keeping is one-way in this panel: there is no un-keep control, so a workspace stays kept.
• Restore brings saved work back. Each row in the Saved Work vault has a Restore button that brings the saved work back as a fresh branch an agent can pick up. The vault keeps its two lists apart — "Unsaved work" (the rescue refs, the only copy of work that was never committed) and "Branch archives" (kept just in case) — and shows a bounded number of the newest of each, so the irreplaceable unsaved-work rows cannot be crowded out by the steady stream of landed-branch archives.
• Changing it is desktop-only. The panel's actions are desktop-only; on a phone or in a browser over Web Access they are not offered.

Related

• Dev Pipeline panel — the panel Work in Flight is part of.
• Dev Pipeline panel (part 2) — the panel's other tabs, including the worktree-cleanup dashboard.
• The paved road — the CLI side of the same worktree record.
• Session isolation — why each session works in its own copy of the project.