# Mid-task intake and work queue

The native terminal's **WORK / QUEUE** section tracks user requests. **TASKS / NOTES** tracks the implementation steps, notes and observed execution layers within a task. Adding a request does not create a fake todo or replace the active objective.

## Incoming requests

Text submitted while a task runs is saved, with its original whitespace and attachment references, before a separate intake reviewer starts. The reviewer uses the configured backend, a bounded snapshot of the current objective and ordered work, a strict response schema, no tools and a total deadline. It cannot execute work or change model configuration. Normal execution continues during review.

The host routes a fresh recommendation as follows:

- **Queue:** retain additional work in the upcoming execution order.
- **Amend:** admit the original request through the existing steering boundary. The host prevents a model from promoting an amendment into a replacement objective.
- **Status:** show the recorded public state in the request's receipt without changing the active goal.
- **Override requested / needs review:** retain the request for a deliberate action. A recommendation alone cannot interrupt work.

“Received,” “reviewing,” “admitted,” and “applied” are different receipts. A new constraint is not effective merely because it arrived. Use **Stop** when execution must stop immediately.

## Controls and presentation

Expand WORK / QUEUE in the right details sidebar. Current work appears first; intake is unnumbered until reviewed; queued requests show their actual execution order. Expand a row to inspect the original message, attachment references, public recommendation and receipts. No private model reasoning is stored.

Eligible requests expose **Queue**, **Apply**, **Replace active**, **Cancel**, **Review again**, and order controls. Apply refines the current objective. Replace active uses the existing safe replacement boundary and retains the predecessor's effects and interruption record. Controls carry request and queue revisions; stale clicks cannot silently act on newer state. Already admitted work uses the existing Stop owner, not a second cancellation mechanism.

`/queue <request>` skips semantic review and explicitly queues future work. `/stop` and Ctrl+C immediately fence root admission, cancel pending intake and queued work, and stop the running owner. A pre-run claim with uncertain preprocessing effects remains held for inspection. Escape pauses without discarding work. In a narrow terminal, the existing **Details** inspector exposes the queue; there is no second task strip or new input-area feed.

Busy-session media is retained with its original path and attachment identity. Queue it to use the existing media preprocessing path. Applying its path as current context is an explicit action; background intake does not inject an unfinished transcription or stale image. Legacy command-started runners retain their existing task/activity presentation rather than receiving fabricated original-request records.

## Persistence and recovery

Requests live in `$OMNIUS_HOME/work-queues/` (default `~/.omnius/work-queues/`), under a hash of the canonical project directory and session ID. Files use restrictive permissions, bounded validated schemas, atomic replacement, revisions and a single root claim. Titles never replace executable originals.

A claim is saved before the existing root drain dispatches work. Actual run, epoch, owner generation and claim identity fence binding and terminal receipts. Exact interrupted-session resume reserves the existing request and checks that the runner adopted that interruption. Unknown effects are not automatically replayed. Proven-dead host processes become held records; live or unverified owners are not seized. Updater checkpoints retain work IDs; a missing referenced ledger record becomes held instead of disappearing or replaying.

A corrupt store, uncertain durable write or writer lock fails closed and is shown as an error. A stale writer lock can require operator inspection/repair; the UI never spins waiting for it or steals an unverified owner. The store retains up to 1,000 requests and 8 MiB per scope; the sidebar shows all live requests and the most recent 40 history items. Older retained history is included in the omitted count.

The renderer retains queue payloads across metric/input frames, so unchanged original messages are not serialized repeatedly. This package changes native interactive intake; browser/daemon check-ins and Telegram retain their existing ingress owners.

## Verification

The implementation contract and acceptance evidence are in `.aiwg/planning/steering-work-queue-20261017/`. Tests use temporary stores, controlled model responses and actual source runner/native terminal implementations. PTY checks cover five terminal sizes, pointer/keyboard controls, Unicode draft preservation and responsiveness while review is pending. These are source tests and controlled terminal fixtures, not live inference or a restarted production daemon.
