Omniscio

The session's journey card — where its work is on the way to master

One narrow, centred card in the conversation, at the point its work last moved — styled like the new-session launch screen — showing the whole trip the session's work is on: the orb glowing in its status colour, the place in line as a big number with how long the work has been ready, the status chip, a plain-English explanation, a row of stage icons, a small branch icon that shows the branch name (with a copy icon) when clicked, who it is waiting on and what clears it, and the refused attempts collapsed beneath; the same card covers cloud sessions, whose trip begins three stages earlier. A session with several branches still gets ONE card: its headline is the branch that needs attention most, and the branch icon reads "2 branches" and opens a list with each branch's own status and time, while on a single-branch card the reveal includes a button that copies the branch name.

On this page

What it is

When a session's work heads for master, the app knows a lot about that trip — and it used to say only one line of it, and only for local branches. The card says the whole thing: the branch's trip as a row of stage icons, the place it has reached, and — whenever it is not simply landing — why it has stopped, who it waits on and what clears that wait. It is a small ticket centred under the conversation, never wider than 320px, so it reads the same on a wide monitor and on a phone.

It is read-only. Its one button copies the branch name; otherwise it has only two fold-outs, one for the branch name and one for earlier hold-ups (each closes with an up arrow), and it renders nothing for a session it cannot say anything about.

Where to find it

Inside the session, in the conversation at the point the work last moved: right after the turn in which the branch was tagged (or landed, or the cloud session left), so anything written later sits below it like any other message — a landed card included, so one that landed hours ago stays at the point it landed rather than under your newest message. It shows up as soon as the branch is tagged — it does not wait for the app's next full look at the queue. If that turn is not on screen (older history, a folded group) it sits by the nearest one that is, and if the conversation list itself is not showing (an empty filter, an empty session) it sits at the foot instead. While the card is on screen it is the only auto-lander entry in the session: no "Auto-landed", "Partly landed" or "Couldn't auto-land" line is drawn — for any branch, any outcome, and every copy, including an earlier land and a card that lists no branch yet (a cloud session's returned work). A session whose card is not on screen keeps its lines, so a land is never left with no signal at all. Once the card is gone (a finished result leaves it after 24 hours) the lines show again, so the conversation keeps its record. The overseer's chat view draws no card, so it always keeps the lines. When a session launched another session, the launching session's card lists that session's branch as one more row — in whatever state it is, from in line to landed, and whether or not the launched session is still running — so a lead can watch its workers' work reach master from its own thread. The forwarded "A branch this session launched…" line is still sent only when the launched session has already closed and can no longer read its own; on the launcher it is folded into the card the same way. There is no menu, panel or setting: if the app knows something about that session's work, the card is simply there. On a phone it works over Web Access like the rest of the session view.

A branch's card belongs to the session that wrote it. When the branch's folder and its ready tag do not say who that is, the app reads the author off the branch's first commit, so a session that only adopted the folder later (an Overseer publishing the work, say) does not get the card.

How it behaves

The orb and the stage icons

At the top, the Omniscio orb sits on a soft glow in the card's status colour — indigo while it waits its turn, amber when it needs a person, ember while it is held, green while it lands. The glow (and the current stage) gently breathes only while the work is actually moving, and never when your computer is set to reduce motion.

Under the explanation is the trip as a row of small round icons, one per stage, left to right, joined by a thin line: a tag for Tagged, a shield for Checks, an hourglass for In line, a merge arrow for Merge, a landing plane for Landed — and for a cloud session a rocket, a cloud and a cloud-download for its first three stages. Finished stages are green, the stage the work is at glows in its status colour, and the stages ahead are grey. Hover an icon for the stage's name (a screen reader reads every name); the explanation above it already names the stage the work is at.

The session is The stages it shows
A local branch Tagged · Checks · In line · Merge · Landed
A cloud session Launched · Running in cloud · Coming home · Tagged · In line · Landed

A cloud session keeps the three stops in front of the branch because its work does not exist on this computer until it comes home. Once it is home, the rest of its rail is read from exactly the same facts a local branch's is, so the two kinds of session can never disagree about where the lander half of the trip is.

The chip

The chip is the pill under the place in line, and it is always exactly one of these:

  • Waiting its turn — ready to merge and in the line. (While auto-landing is switched off on this computer it says so instead, and shows no slot: no turn is coming.)
  • Held — the auto-lander has it and is working on it, or is holding it for this pass. Nothing is needed from you. An answered dependency sign-off reads Held too — you decided, and the lander owns it from that moment.
  • Landing now — it is being merged onto master. On the rail this is the Merge stop for a local branch, and the Landed stop for a cloud session — the cloud rail has no Merge stop of its own, and landing must read as landing rather than as waiting in line.
  • Landed — merged onto master.
  • Needs a person — nobody automatic is going to move it: a merge conflict handed back for a rebase, a give-up the lander recorded, a hold only a person can release, or a sign-off only you can give.
  • Possible secret — a safety check found something in the changes that looks like a credential, so it stopped before landing. It has its own pill because its fix is its own: remove the secret from the changes, then mark the branch ready to merge again.
  • Running remotely / Coming home — the two cloud stages, before the work is on this computer.

The counts

Under the orb is the branch's place in line as the big number (#4, of 17) whenever it holds a slot, and beneath it how long the work has been ready (ready 4h ago). Once it has landed that line goes away and the age moves into the green chip itself — Landed · 2m ago. A branch waiting on a person holds no slot, so it shows no number, only the age. The place is said once: the explanation never repeats it. The ages read from the ready tag's own set-at:; a legacy tag without it simply shows less. This line carries TIME, never the chip's own word — the pill below it says that.

The explanation

Whenever the trip is not simply running, the card says three things in plain English:

  • what went wrong — quoted from the app's own record of the decision, never a code, a file path, a test name or a security scanner's finding;
  • who it is waiting on — you, the auto-lander, or the machine;
  • what clears it — the action, or the plain statement that nothing is needed from you.

For a cloud session whose changes came home on a branch that nothing tagged, the card says so on the same card — no stage is shown as the current one, because the step that branch never took is exactly the one that would have been, and the explanation is that nothing has marked those changes ready to merge.

The history

Held back under the explanation, collapsed, is the branch's own record: "N earlier hold-ups", each with when it happened and the lander's reason. Open it to see the whole sequence — a branch that has been refused four times should not look like one that was refused once. The line carries a small mark, a chevron while the list is closed and a plain ✕ while it is open, and clicking it does either. Hovering a row shows the exact time, not just how long ago.

Refresh

The card updates as things actually move — on the auto-lander's own change, on a land the app recorded after the fact (a dropped land its landed-stamp sweep re-recovers, or a hand-land reported to it), on a cloud capture starting or finishing, on an approval being decided, and whenever you open the session. While you are watching a trip that has not finished, it also re-reads on a slow bounded cadence, so a place in line can never go stale without limit while it is on your screen. A landed branch goes quiet at once.

It reads only the session you are looking at. The read asks the app for that one session and the app answers with that session's rows alone, so a phone watching one conversation is never sent what every other session is doing. Two of the pushes it follows name no session at all — the lander's own state and a pending approval — so either of them re-reads the session on screen; the third names a session and is dropped before it can refresh anything when the name is not this one. A panel you are not looking at makes no call at all, and a session you have already viewed keeps its last card on screen while the fresh one is on its way, so switching conversations never blinks the card — or the land notices it suppresses — out and back.

When the session finishes its work another way

A session that finishes its work through unified work finishing — landing it, opening a pull request, keeping the branch, tagging it, or running its own finish command — gets the same ticket, never a second panel. The chip and headline say where the finish is in plain words (Getting ready, Waiting its turn, Landing, Landed, Needs you, Blocked, Failed), the stops follow that road, and earlier finishes sit in the same fold-out.

  • A pull request is followed until it merges. Opening it is not the end: the ticket reads Waiting to merge, with a Merge pull request… button that opens the app's confirm dialog, until the pull request is merged (green) or closed without merging. A draft gets no button.
  • Export approval shows an Approve export button only on the computer that will finish the work; anywhere else the ticket says it is waiting for approval there.
  • Work built on a linked computer shows its trip home: waiting to come home, coming home, landing, landed, or could not come home.
  • One card per session. When the AutoLander already has a card for the session, the finish is a single Finish line on it (with its button, when the card has none).
  • Nothing to finish, no card. A session that never finished anything, a project that is not a code repository, or a computer with work finishing switched off shows nothing — no empty warning.

dev-pipeline-panel.md shows the auto-lander globally — its queue, live status and land history across every repo — where this card is that same data narrowed to the one session in front of you. For the rest of what this library holds, INDEX.md is the map.

Last verified 2026-11-18