Omniscio

Inbox overseer gate (hold new items for one Overseer to screen)

Turn it on, name one Overseer, and new things that need you wait a few minutes for that Overseer to look at them first — what it can answer itself never reaches you, and everything it handled is visible, with its reason, from a chip in your inbox header. Nothing is ever lost or deleted: a held item is exactly the item it would have been, only the moment you see it changes, and a folded "Holding now" section at the top of the inbox sidebar lists every held item, where clicking one hands it straight back to you. Anything the Overseer has not dealt with comes to you anyway when the time runs out, and the gate is off by default, so while it is off your inbox behaves exactly as it does today.

On this page

What it is

An Overseer is an agent you run that watches your fleet and answers other agents for you. This feature lets ONE of them also screen your inbox. Instead of a new session finishing a turn, or a new card being raised, landing straight in front of you, it waits a short while on that Overseer's desk. The Overseer looks at it and does one of three things:

  • Lets it through — it appears to you as it normally would.
  • Puts it away — it decided this is something you need not see, and records why.
  • Does nothing — and when its time is up, the item arrives to you anyway.

The point is that the arrangement becomes something you can check rather than something you take on faith. An answered session and a silenced card used to look identical to one that was never raised. With the gate on, both what is waiting and everything the Overseer already handled are readable, so its silence is something you can prove rather than trust.

  • It is not the same as the alert grouping an Overseer already does. That one briefly batches related alerts so duplicates and near-duplicates arrive as one thing. This one holds a single item for a single decision, and records that decision.
  • It does not hold work. The hold exists so an Overseer can glance at one item and decide, not to park things until it gets round to them. Its default is ten minutes.

Where to find it

  • The switch is on the Overseers hub, in the "How they behave" settings. One toggle turns the gate on, and a slider sets how long one thing may wait on the Overseer.
  • What is being held is a section in the inbox sidebar, sitting just above the list: one collapsed row reading "Holding now" with the number being withheld. It appears only while the gate is on AND something is actually being held — with nothing held (including when no Overseer is running) there is no row at all — and stays folded until you open it. Opened, it lists every held item — its name, whether it is a session or a card, and how long until it reaches you on its own.
  • What the Overseer already handled is a chip in the inbox header — the row at the top of the inbox where the title sits. It appears only while the gate is on AND its Overseer is actually running — with no Overseer running there is no chip at all — as a small shield icon with the handled count beside it, styled like the header's other icons (hover it for "What the inbox overseer already handled for you"). Clicking it opens a small panel listing what was dealt with, each row with its disposition and a one-line reason.
  • Releasing one item is clicking it in that sidebar section. It works at any time, with no confirmation, and it does not depend on the Overseer being alive — the item comes back to your inbox the moment you click, and opens for you. There is also a rebindable keyboard action for it (Settings → Keybindings), with no default key set; while the section is open it releases the newest held item.
  • The Overseer reads and acts on what is held over the command line, not through the app: GET /overseer/gate/held lists what is being held, GET /overseer/gate/handled walks back the history, and POST /overseer/gate/release and POST /overseer/gate/dispose end a hold. Those two POSTs refuse every caller that is not the named Overseer, so no other agent can quietly clear something out of your inbox.
  • GET /overseer/held is the same question asked by the audit surface, and it answers from the same live hold records the gate route does — the two can therefore never name different items. It also names WHICH Overseer took each hold, which it reads from the action ledger: a live hold records no acting slot (that is written when the hold ends), so the ledger is used to label a hold, never to decide whether one exists. Until 2026-10-11 it did decide, from the ledger alone, and it reported 48 items held against a queue of zero — every one a hold whose expiry had ended it without the ledger recording a release.

How it behaves

It is switched off until you switch it on. While it is off, nothing is held, no item's delivery changes, and every existing path behaves exactly as before.

A hold always has an expiry, and the item itself honours it. Even if the background pass that releases expired holds stopped running entirely, a held item would still arrive on time, because the reader that decides whether an item is visible checks the expiry itself. A dead part of the machinery can never turn a hold into something permanent.

Nothing is held when there is nobody to read it. If the Overseer you named is not running, is paused, is stood down, or has stopped itself over spending, the gate declines to hold and the item comes to you. An item waiting on an absent Overseer would be a delay with no purpose.

A sleeping Overseer is woken the moment something lands on its desk. An Overseer that has nothing to do goes quiet between its scheduled check-ins, so a held item used to wait for the next one. Now the arrival wakes it: it looks at what was held straight away instead of minutes later. The same is true of the older screening hold used when this gate is switched off — an alert parked there asks the Overseer to judge it immediately rather than at the half-way point of its window. A burst of arrivals wakes it once, not once each; and an Overseer that is in the middle of a turn is never interrupted — the arrival is queued for its next turn boundary, or waits for the hold's own expiry if the queue cannot take it.

Nothing is held for an Overseer that has stopped screening. Being switched on is not enough: the gate also checks that the Overseer at its address has actually been dealing with what it was handed. If three finished holds in a row, all made since that Overseer took over, ended with nobody acting on them, the gate stops holding and items flow straight through until it is working again.

  • Only the current Overseer counts. Holds made before it took over are ignored, so moving the gate to a different Overseer gives it a clean slate rather than the last one's record.
  • One real review resets it. The moment the Overseer releases or puts something away, the gate holds again — this is a valve against a silent queue, not a permanent judgement.
  • Releasing items yourself does not reset it, because that is your work, not the Overseer's.
  • It retries on its own once a day, so an Overseer that recovers is used again rather than being left out of the loop for good.
  • It costs a short delay to find out. The gate needs three holds to finish before it can tell, so an Overseer that has gone quiet still delays what arrives during those holds — about half an hour at a typical volume. After that, nothing more is delayed until the daily retry.

Held things are never deleted or rewritten. A release puts the item back exactly as it would have arrived — it kept its own status and its own question the whole time it was held, so there is nothing to restore. Putting something away archives it rather than destroying it.

An item that skipped its review says so. If a hold's time runs out with the Overseer never acting on it, the item arrives carrying a small "Not reviewed" mark on its row — so a delayed item can never be mistaken for one that was screened. An item the Overseer actually released carries no mark: the mark means "nobody looked at this", not "the gate touched it". It clears when the next thing arrives on that session.

It only screens its own project. The gate withholds only items belonging to the project the screening Overseer works in. An item from any other project — or one with no project at all — goes straight to you, untouched, and is never held, released or put away by this gate. Reaching into a project its Overseer was never asked to look at is not this feature's to do.

A few classes are never held, whatever the settings say. Money and billing, security and credentials, and anything you scheduled or are waiting on always pass straight through. Anything the Overseer says to you, or raises for you, is never held by its own gate — that would be a loop with no exit. Permission requests and plan approvals always come straight to you too, because those are your decisions and nobody else's.

You can add your own pass-through entries. A setting holds a list of entries; anything whose key matches one, or begins with one, is never held. An entry for a whole family of alerts therefore waves through everything from that producer. The list ships empty.

A flooding producer cannot build a wall out of your inbox. If the number of things being held at once reaches a fixed ceiling, the gate simply stops holding anything new until the backlog clears, and items flow straight through. This is a safety valve rather than a volume control.

Every skip has a name. The gate counts one event per outcome, so a near-zero hold rate can be read as a specific reason — nobody to hold for, unhealthy, not an item it screens, an owner-critical class, on your own pass-through list, the ceiling, an Overseer that has stopped screening, the Overseer's own traffic, or a session that was already waiting on you — instead of looking like a quiet success. (A gate that is switched off is not among them: it refuses before it decides, so there is nothing to hold and nothing to count.)

Off by default; the two on-screen controls are the switch and the hold length. Which Overseer runs the gate, and your own pass-through list, are live settings that do not yet have a control on the settings screen. Left alone, the gate uses your global Overseer and the built-in protections only.

  • overseers.md — what an Overseer is, what it watches, its heartbeat and its spend cut-off.
  • inbox-alerts.md — the short-window batch hold that groups related alerts before they reach you.
  • Sending alerts to an Overseer — how a class of alert is handed to an Overseer from the card, and why the assignment survives a restart.

Last verified 2026-10-22