Omniscio

Unified work finishing

How a session's finished code leaves the session: one finish chosen per session at launch (land it on local master, open a pull request, keep the branch, a tag or the team's own command), a standard per computer that picks it by default, and a plain instruction telling the session how it finishes.

On this page

When a session's coding work is done, the app — not the agent — finishes it the one way that session was given at launch, and the session's card shows where the work actually ended up.

Turning it on

Open Settings → Dev Pipeline → Unified work finishing:

  • Enable unified work finishing enrolls newly launched sessions. Off by default; turning it off never changes a finish that has already started. A session launched while it was on, whose finish never started, goes back to the old finish while it is off — so npm run pr -- --push works for it again. A session started in a project with no code repository (Ask Omniscio, a Mind Map chat) starts normally with no finish, since it has no code to finish.
  • Pause finish actions stops new finish actions while status keeps updating.

A finish standard for each computer

Finish standard per computer has one row for This computer, Cloud machines, Any linked computer, and one for each linked computer by name. Pick a finish for a row — Land it puts the work on local master, Open a pull request sends it to GitHub — or leave it on Follow the project's setting. A named computer's row beats the any-linked row.

The finish a new session gets is decided in this order:

  1. the choice made for that session,
  2. a project and computer preference,
  3. the computer's standard,
  4. the repository's own default.

A row whose finish the repository cannot run (a team command with none set up) is skipped.

What the session is told

Every enrolled session's instructions end with How this session finishes its work: its finish, where it was chosen, where the work completes, and the one place it hands finished work to. The session never tags, pushes, merges or opens a pull request itself, and it counts its work done only when the finish succeeded with a receipt. While unified work finishing is switched off, a session whose finish has not started on the new road gets no such section: it finishes the usual way.

Handing work over takes three calls, in this order, once the work is committed. The session first reads its finish for the intent revision, repository and base. It then asks for preparation, which runs the repository's own gates against the exact commit and can take many minutes; it then submits once, carrying the references preparation returned. The instructions name every field each call needs. A session that submits before preparing is answered with a blocked result naming the preparation step — never a crash — so it can prepare and submit again.

A refused call says why. A caller that is not allowed (not bound to the session, or the person must approve) is answered 403, and any other refusal 409, each with its own code and a plain sentence. A failed check run answers one fixed sentence rather than the checks' raw output. Only a real fault, such as the database being unavailable, is a server error.

The checks and the pull-request finish always run from the Omniscio checkout the app finds the same way the lander does. If this computer has no Omniscio checkout, the call is refused with finish-checkout-unavailable and the finish shows as blocked, rather than failing part-way.

Where you see the outcome

The session's journey card shows where the finished work ended up — see Session land status strip.

Last verified 2026-11-18