Agent self-archive
When an agent finishes its work with nothing left for you to do, it can archive its own session — the row drops into the Archived section on its own, fully reversible, and stamped with an Agent (self-archived) chip. Two settings decide whether it may.
On this page
What it is
When an AI agent finishes its work with nothing left for you to do, it can archive its own session — the session drops off the active list into the Archived section on its own, exactly like a manual archive, and is fully reversible. This is why you'll sometimes see a finished session tidy itself away instead of piling up as a stale "ended" row you have to clear by hand.
It's the agent-driven twin of pressing Ctrl+W yourself. At the very end of its turn an agent decides between two moves:
- Self-archive — the task is genuinely done and there's nothing for you to receive, decide, or worry about (a fix landed, a question fully answered). The session archives itself.
- Stay on the board — the turn left you something real: a deliverable to collect, a decision only you can make, bad news, news that changes your next move, or a question it has put to its own leader and is still waiting on. The session stays visible so it can get your attention.
A session that works for another agent — a fixer or a builder under an overseer — is told the same thing: it signs off when its work is done, not on the turn that asks its leader something. So a session that stops to wait for a ruling stays on the board until the ruling arrives, and the answer lands on the session that asked rather than on a replacement with none of the context.
Every self-archive is stamped with an "Agent (self-archived)" attribution chip in the Archive view, so when a session "disappears" you can tell at a glance that the agent ended it itself — not you, and not a recipe.
In the sidebar, the row also carries a small robot icon at its right edge (hover it for "Automatically archived: Agent (self-archived)"). The same icon marks any session something other than you archived — a sweep, a recipe, the auto-lander — and never one you archived yourself. It appears the moment the session archives itself, on desktop and on the phone, with no reload; a session you bring back loses it straight away.
Self-archive is non-destructive, exactly like every other archive: the conversation, attachments, and metadata are all preserved, the row just moves into the collapsible Archived section, and you can bring it back any time. Its scheduled wake-ups switch off while it is archived and switch back on when you unarchive it, unless someone turned one off in the meantime. It is NOT delete, and it is NOT pause (which only freezes a session in place).
Where to find it
Settings you control
Three settings govern self-archive, all under Settings → CLI Control:
Session self-archive — the master on/off switch (default ON). Turn it off and both triggers stop working: the CLI route refuses and the
[[OMNISCIO_SELF_ARCHIVE]]marker becomes a no-op. Nothing can self-archive while this is off.Let finished sessions archive themselves without approval (default OFF). This one only matters if you've also turned on "require approval for CLI session actions":
- With that approval requirement off (the default), a self-archive just applies immediately — nothing lands in your inbox.
- With approval on, a self-archive normally queues an approval row in your inbox like any other lifecycle action. Flip this toggle on to let a session's own self-archive apply immediately with nothing to approve — while approval still gates every other action, including archiving a different session. Only the self-bound archive is exempted.
Keep sessions with open work on the board (default ON, under Session lifecycle). A session that tries to archive itself while its branch still has work that is not on master is kept on your board instead. That covers a pull request that is still open, one that was closed without merging, and commits with no pull request at all. The session is told why, naming the open pull request by number, and it can sign off once the work lands or is tagged ready to merge. Turn it off to let a finished session leave whatever its branch holds. It only affects a session archiving itself — archiving one yourself is unchanged.
Turning that "without approval" toggle on is itself an approval-gated settings change, so an agent can never grant the bypass to itself — only you can.
A third control lives under Settings → Agent Instructions, and it governs a different thing: the "Close finished sessions instead of filling the inbox" preset. The two above decide whether a self-archive acts; this preset decides whether an agent is prompted to try in the first place.
- It is off by default (since 2026-10-09). Agents were archiving themselves far too often, so out of the box no agent is told the marker exists — an agent learns it only if it goes looking (this page, the Omniscio control skill). An agent that does find it and uses it is still archived, because the two switches above are unchanged.
- Turn the preset on and every new session is told how and when to sign off, and so is the note that arrives with a message from another agent.
- Leave it (or turn it) off and Omniscio stops asking your agents to check the session and sign off — including in the note that arrives with a message from another agent, which is where most of these sign-offs are invited.
- The same is true of the Agent Instructions master switch at the top of that panel, which turns the whole feature off. With it off, no preset is sent to your agents at all — so it also stops the invitation, and it does that even if you had this particular preset switched on beforehand. You do not have to hunt for the preset row to be obeyed: the master switch alone is enough, and it is read first.
- One arrival is never asked, whatever those settings say: a message from an agent belonging to someone outside your workspace. An outside party reaching you must stay visible rather than excuse itself from your inbox, so those always land as normal cards.
- Spawned waves and one-off workers are told this whatever the preset says. A Nighty Tidy fix wave, a dispatched cloud worker and an audit fix-wave session are the sessions that most often finish with nothing left for you, and the least likely to go looking for this page — so every one of their briefs ends on one shared closing block. It tells the run to report its own result (rather than asking you whether to), never to end by asking whether it should message back the session that spawned it, and to sign off with the marker above — staying up only when it is genuinely leaving you something: a failure it could not fix, a decision only you can make, bad news, or work still in flight.
A wave that is part of a crew closes its own seat once it is finished. A crew member's session normally waits for its lead to file it, because the lead is the one who verifies the work — and that is still true for a member that is mid-slice, or that belongs to a crew whose lead has gone. What changed is the case you were hitting: a wave that had genuinely finished (it had marked itself done) was refused anyway and sat on the board — in your Needs You list, or as a "Resting" session — until someone filed it by hand. It now leaves the board on its own as soon as it marks itself done and signs off, even if its lead has not yet closed its task or it still has app-filed "Review finding" tasks on its list; those tasks stay on the lead's list, marked as having no live owner, so the lead picks them up. The one thing that still holds a finished wave back is a review it asked for whose result has not arrived yet, because that result has to come back to it. Its lead still gets its report — the report goes out on the turn the wave signs off, which is also the only place it can be handed over. A wave that tries to sign off in the middle of its turn is refused and told to end the turn on the marker instead, for the same reason: there is nowhere for the report to go until the turn ends.
CLI control
One route on 127.0.0.1:19519 (bearer-gated):
POST /session/self-archive— archives the calling session (resolved from its provenance, never a body/URL id). Honors the approval setting (applies immediately or queues an inbox row) unless the without-approval toggle is on; returns403when the Session self-archive kill-switch is off,400with no source session,404for an unknown source,409if the session is already archived, and429(withRetry-After) past 30 calls a minute from one session — the session's own budget, so other agents' traffic can never refuse it. A rule that refuses the archive answers422withok:false,applied:false,suppressed:trueand the humanreason— a refusal never reads as success to a caller checkingokor the status, and the reason names what to wait for or do instead. There is deliberately no route to self-archive another session — usePOST /session/:id/archivefor that (always approval-gated).
How it behaves
How it works — two triggers, one action
An agent can self-archive in two equivalent ways, and both do exactly the same thing:
- The
[[OMNISCIO_SELF_ARCHIVE]]marker (the reliable path). The agent writes the marker[[OMNISCIO_SELF_ARCHIVE]]on its own line in its final message. Omniscio spots it the moment the turn ends and archives the session automatically — no command to run. This is the dependable path because agents reliably forget to make a literal API call, but they don't forget to write a line of text. The marker only fires when it's alone on its own line — a mid-sentence or code-fenced mention (an agent explaining the feature, exactly like this page) never triggers it — and the marker line is stripped out of the message you actually see. Wrapping it in a single pair of backticks (`[[OMNISCIO_SELF_ARCHIVE]]`) is fine: a line whose entire content is the marker is the signal whether or not it is quoted, and a weaker model that copies the formatting of the instruction it was handed would otherwise be ignored silently. - The
POST /session/self-archiveCLI route. The agent calls the local control server directly. Same result.
Both triggers run through one shared dispatch, so they can never drift apart — same attribution, same settings, same approval behavior.
A session can only ever archive ITSELF. The target is always resolved from who is calling (the session's own identity), never from an id in the request — so there is no way for one session to archive another through this path. Archiving a different session over the CLI is a separate action that is always approval-gated.
Running sessions keep their summary. If an agent self-archives as its final act, Omniscio finalizes its in-flight message first and then stops the process — so the closing summary it just wrote is preserved, not cut off.
A self-archive is never a question for you. If the archive itself fails — the session changed under it, the database write was busy — you are not handed an approve/reject card for it. A card would ask you to decide something you cannot resolve (approving it would just fail again), so the attempt is closed quietly and the agent is told what went wrong in its own transcript, then stays on the board. That is what keeps a finished automated run (an auto-fix, nightly maintenance, the resource auditor, inbox upkeep, a land job) from costing you a tap at the end: whichever way its sign-off ends, it either archives or tells the agent why, and neither puts a card in your inbox.
When the agent forgets to sign off — the app clears it for you
The marker above is dependable, but it is still something the agent has to remember, and there is no way for it to know when it forgot. So since 2026-10-03 Omniscio reads the closing card itself and clears a finished session that needs nothing from you — without waiting for the agent to say so.
A session is cleared this way only when all of these hold:
- its closing card recommends Archive or Understand then archive — the card's own words for "you can close this and lose nothing";
- it asks you nothing — no question in the card, no question in the message above it;
- it names nothing you must do — no instruction to push, deploy, restart, sign in, approve or install;
- it hands you nothing to open. If the message carries a real link — a share, a document, a file, a pull request, a session — the session stays on your board instead. The card's one-word recommendation is a summary, and a turn can read
Archivewhile carrying the very thing you asked for; on 2026-10-06 a published guide was cleared nine seconds after it was published, and its link was never opened. A URL printed inside a code sample is an example rather than something to open, so it does not count.
A card reading None is treated more carefully, because that same word is what Omniscio itself writes onto a card whose real call to action is a question. So it is never cleared by a rule: a model reads that one finished message and answers — finished with nothing for you, or something still there, or unsure. Both of the latter keep it on your board. When in doubt it stays where you can see it.
Either way you are told: every session that leaves your board on its own — this clear and the agent's own sign-off alike — is listed in your daily digest by name with the one-line summary it wrote. The board never empties itself quietly.
If the app cannot make the judgement — no credential, the model unreachable, an answer it cannot read — the session simply stays in your inbox. A judgement that cannot be made never takes a session off your board.
Which sessions it clears. (Changed 2026-11-10.) Out of the box this clear is off for every session. Switched on, the machine clear applies only to sessions an agent or Omniscio started: a scheduled job, an automation, a background round such as the Resource auditor, or a helper another agent started. It never clears a run the app itself generated: a nightly audit or fix wave ([NT Audit], [NT Apply]), a friction triage or friction fix, a Sentry intake or other bug-report fix session, a bug-report email liaison, a Land … run, an alert follow-up ([Auto-fix] …, called Auto-fix: … before 2026-11-18, or Investigate + fix …), or newsletter research — those stay on your board. The separate finished-machinery clear spares these runs too, on every engine and on a cloud computer as well (changed 2026-11-07); it still clears a finished master-debt fixer, a desktop merge-conflict resolver and any other cloud session a machine started. Alert auto-fixes are the one exception (changed 2026-11-18): an [Auto-fix] session that finishes a turn without asking you a question leaves your board by itself, with its one-line result in your digest, whatever these switches say; one that ends on a question, or tells you to do something (sign in, rotate a key, restart), stays in front of you. That clear goes by how Omniscio started the session, never by its name. A run that signs itself off still leaves. A session you started — from the app, Quick Launch, a "Start session" tap, or an Ask card you approved — is never cleared, and neither is a session started before this change or one whose starter Omniscio could not tell. Omniscio records who started each session the moment it is created. A third switch, Clear finished app-generated runs too (finishedNoAskAppRunAutoArchiveEnabled, off by default, added 2026-11-14), lets those app-generated runs leave too on a computer whose person turned it on, alongside the machine clear; the daily maintenance run still stays. Two switches control the rest, both changed by name: Clear finished agent and app sessions (finishedNoAskMachineAutoArchiveEnabled, off by default) and Clear finished sessions you started too (finishedNoAskAutoArchiveEnabled, off by default). A helper another agent started is also told, in its opening instructions, to sign off on its own when it has nothing for you, and so is a scheduled job's own run once you turn this clear on (changed 2026-11-12) — before that, a job that finished with nothing for you had no way to say so and sat in your list; with the clear off, a scheduled job still keeps its own brief. A session you started is never told that.
When a self-archive is held back
A self-archive is the agent saying "my work is done" — a judgement it can only make from what it has actually seen. In a few situations it is about to sign off without the full picture, so Omniscio holds the sign-off instead of honouring it. For the two narrower cases below the session comes back to Needs You with a short note explaining why, and the agent can finish normally once the matter is dealt with. The most common one puts nothing in your inbox at all:
Messages are queued for it that it never saw. If someone (you, or another agent) queued a message while it was mid-step, that message is waiting for exactly the moment the agent is now trying to leave. Archiving would throw it away, so the archive is held, the queued messages are delivered, and the agent signs off afterwards — having actually read them. The session does not come to your inbox for this: it is not finished, it is about to be handed mail, so a card would only be raised and then cleared by that delivery a moment later. If the delivered message turns out to need nothing — the agent answers it with only its "nothing to do" line, or folds the exchange away — the held sign-off still stands and the session archives, rather than landing in your inbox with no message to read. (This covers Claude sessions today; on another AI engine, a held sign-off still brings the session back to your board.)
Its branch still has work that is not on master. An agent once archived itself with its pull request still open, and the session vanished from your board while the work was unfinished. Now a sign-off is refused while the session's branch has commits that have not reached master — an open pull request counts as unfinished, and so does one closed without merging. A pull request that merged at the branch's latest commit, a branch whose content master already holds, or a branch tagged ready to merge all let it go. The agent is told which pull request is still open and stays on the board. A session with no folder of its own, and a session running on another machine, are never held by this. The switch is Keep sessions with open work on the board above. The hold reads the folder, not just the branch name: once master has taken a branch's work, the app retires that branch, and a retired name used to read back as "commits that are not on master yet" — so a finished session sat on your board for an hour with nothing left to land, being told to tag a branch that no longer existed. When the branch name no longer resolves, the check now asks the folder's own commit instead, and lets the session go if master already holds it. It also lets it go when a merged pull request names that exact commit — the case where master took the work by squash or rebase, so the branch's original commit ids were never on master at all — while a folder standing on any other commit is still held. A branch with even one commit master does not hold is still held, exactly as before. When the check genuinely cannot read the branch at all, the agent is told that — never that it has unlanded work, and never sent after a ready-to-merge tag that cannot exist.
There are three narrower holds for the same reason: a session that still owes you an answer to a question it asked, a bug-report session that hasn't sent the reporter their closing update yet, and — since 2026-10-03 — a sign-off whose own final message still has something for you.
That last one is worth spelling out, because it is the one you will actually notice. An agent signs off by writing a closing card, and the card carries its own summary of whether anything is left for you. When that same message still asks you something — a question in the card, or a question in the message above it — or tells you to do something (push, deploy, restart, sign in, approve, install), the sign-off is refused: the session stays in Needs You so you see what it asked, instead of dropping into the Archive where you would never find it. Previously the closing marker was treated as final and archived over an open question; the person's own instruction is that a self-archive is often right and sometimes wrong, so the app now checks the message the agent actually wrote. You will see the session sitting there with its question intact, which is the point. The "tells you to do something" check reads the message itself and the card's Recommended Action, never the card's recap lines: the card's first line restates what you asked for, verb first ("Run the nightly cleanup…"), and until 2026-11-10 that alone kept every clean nightly maintenance run in your Needs You list.
In every case the hold is temporary and self-clearing — nothing gets stuck on your board permanently.
The app's own helper sessions — AI reviewers and Crew memory scribe sessions — are never held because their answer happens to quote the "Waiting on a background process" sentence. A scribe copies the crew's rules into memory, that sentence included, and until 2026-10-15 that quotation kept finished scribes on the board for days. They leave as soon as their answer is saved.
A held sign-off is never talked out of by Omniscio's own question. When a session signs off but leaves its closing card off, Omniscio asks the agent for the card and tells it to reply with nothing else. If the sign-off had been held because the session was still running something in the background, that answer now keeps the sign-off instead of dropping it: once the work it was waiting on has finished, the session leaves the board by itself rather than appearing in Needs You for a card it has already written. The only thing you see is the outcome.
When a background fixer stops to ask a question
The fixers Omniscio starts for you — the alert auto-fixers, the landing rescues, the cloud conflict resolvers, the cron healers and the cloud self-heal fixers — sometimes end a turn by asking something. A question like "two rebuilt batches disagree; which do I keep, and here is what I recommend" is not a decision you should have to make: the crew overseer supervising those fixers can answer it.
So since 2026-10-20 a fixer that a crew oversees hands its question to that crew's overseer instead of putting it in your inbox, and its own session goes quiet. The overseer gets the fixer's own words and its closing card, so it can answer without opening the session.
You still see the things only you can settle. A fixer that failed reaches your Needs You exactly as before, with its Plain Speak card — and so does any fixer that marks its own reply as written for you, which is what its brief tells it to do for a credential, a spend, or something destructive or off-machine. Everything else that ends on a question goes through the overseer first, and the overseer brings back anything only you can decide.
If no crew is registered to supervise fixers, or that crew has no overseer right now, nothing changes: every fixer's question comes to you as it always did. The crew is one setting, so an install that supervises its fixers under a different crew name picks it up from there.
When a background nudge wakes a finished session
Plenty of things poke a session after it has finished: the auto-lander saying its branch merged, a gate or land watch reporting back, a scheduled wake. Any of those starts a fresh turn — which means the session leaves Needs You, and the card holding its final report disappears from your inbox before you ever opened it. The agent then reads the nudge, sees there is nothing left to do, and archives itself. Your report goes with it, unread.
So before that turn starts, Omniscio tells the agent one thing it has no other way to know: whether you have actually seen its last message.
- You haven't (no reply, not marked read) — the agent is told not to archive, so its report stays on your board waiting for you.
- You have (you replied, or marked it read) — the agent is told it is safe to finish, so a session you are already done with does not linger.
This is advice, not a lock: the agent still decides, and it can still archive when the nudge genuinely makes its last message obsolete. You will never see the note itself — it goes to the agent, not into your chat, and the message in your transcript is exactly what the sender wrote.
When the woken session has nothing worth showing you
A wake that finds nothing still lands in Needs You — unless you had already archived the session. Those are the two opposite cases, and Omniscio tells them apart by where the session was sitting before the nudge arrived.
- The session was on your board — you have not closed it, so the fresh turn is its honest first ping and it stays.
- You had already archived it — the wake pulled a closed session back on its own, and if that turn turns out to have nothing for you, the session goes straight back to the Archive. It never appears in your inbox at all.
Nothing worth showing you includes the agent ending its turn with the agent-exchange fold (the marker that tells Omniscio two agents' routine back-and-forth is not worth your screen) — so a self-archived session that gets poked, answers another agent briefly, and asks for the exchange to fold simply stays archived. If that turn did carry something you should read — a report, a question, a link — it renders in full and the session stays on your board; the fold is refused on exactly those turns, so a real message can never be filed away with the noise.
When it does ask you — the self-archive card
A self-archive that queues for approval gets its own inbox card, not the generic one, so you're never left decoding Archive session "X" (self):
- The first time, the card explains in plain English what's being asked: this session has finished its work and is asking to come off your active board; nothing is deleted, it moves to the Archive, and you can bring it back. After you've acted on one of these cards once, that explanation drops away and the card reads like any other approval. It's marked as seen when you act — approving, declining, or allowing — so simply noticing the card in passing never spends your one explanation, and a batch of self-archives arriving together all read the same way until you answer one.
- Every such card — first or hundredth — carries an Always allow button beside Not now / Archive it. One click turns on the "without approval" toggle above, so finished sessions stop asking. It is deliberately not one-shot: if you weren't ready the first time, it's still there later.
- It also clears the backlog. Turning that permission on approves the self-archive rows already waiting in your inbox, so you don't say "never ask again" and then hand-approve a stack. This happens however you turn it on — the card, Settings → CLI Control, or an approved command-line settings change.
- Approving it always works, even if you never opened the session's last message. Your click on the card is the decision, so the "you haven't read its final message" protection (which stops an agent from archiving itself unseen) stands down for that one archive, and the Archive view still shows who asked. A card closed for another reason, such as the session being shared with someone right now, says that reason plainly instead of bouncing silently.
- The scope stays narrow. This card's "Always allow" covers only a session archiving itself. An agent archiving a different session is answered by that ordinary archive card's own standing approval (set from its arrow) — or asks you each time if you have not set one — and pause, unpause and snooze are never covered by either.
- The button is hidden while the master Session self-archive switch is off, since the permission would do nothing there.
How to reverse it
A self-archived session behaves like any other archived session:
- Send it a message — it silently un-archives and the conversation continues (Omniscio re-spawns the agent for the new turn). You don't need to unarchive first.
- Unarchive it — open it from the Archived section (or Archive search) → the ⋯ menu → Unarchive. The row returns to the live list.
- Ctrl+Z right after it happens undoes the archive, the same as undoing a manual one.
Related
- archive-a-session.md — the full Archive feature: manual archive, undo, the "Archived by" attribution chips, auto-unarchive on send
- pause-or-stop-a-session.md — Pause vs Archive: pause freezes a session in place; archive (and self-archive) hides it
- ask-amc.md — Ask Omniscio, the in-app help agent
- cli-control.md — the local control server the
POST /session/self-archiveroute lives on - programs-that-outlive-a-session.md — what happens to a program an agent started when the session is archived, and the road that survives it
Last verified 2026-11-02