Mid-stream messaging and interrupting a running session

What it is

An AI session spends most of its time working, not waiting on you. This area covers the two things you can do while that is happening, and they are two halves of one idea: keep steering, or stop this turn.

The first half is mid-stream messaging — handing a running session another message. Because the session is busy, your message cannot be acted on the moment you send it, so Omniscio holds it and delivers it at the next natural pause, when the current turn finishes. A message handed to a running session is never silently swallowed: you can see it waiting as a queued row. The composer's own send control changes its wording while the session runs, to warn you that sending right now is a different action — it would interrupt the current step instead of waiting.

The second half is interrupting — stopping the turn that is running right now. Interrupting stops the current turn; it never ends the session and never discards the conversation. The session stays open and ready for your next message. Because throwing away a turn's work is expensive to undo, both ways of interrupting are deliberately hard to trigger by accident.

Where to find it

• Open a session and look at the composer, the textarea pinned to the bottom of the panel. While the session runs, its primary send control is labelled to say that a plain send would interrupt the current step, and a Stop button appears beside it.
• The Escape key interrupts the active running session from anywhere in the app.
• A message you hand to a running session shows up in that session's queue list, collapsed by default with a count of how many are waiting.
• Every key, including the interrupt key, is listed and can be rebound in Settings, under Keyboard Shortcuts.
• A session whose turn or process stopped on its own, rather than because you stopped it, is grouped in the sidebar's Interrupted section.

How it behaves

• Send a message — the composer itself: typing, sending, attachments, and the running-state warning on the send control. This is where mid-stream messaging starts.
• Queue a message — the option that lines up a follow-up to send itself the moment the agent finishes, plus the queue's own rules and limits.
• Pause or stop a session — the four different ways to stop a session, including interrupt, and which one to reach for.
• Keyboard shortcuts — the interrupt key among every other binding, and how to change one.
• Aborted-response recovery — what happens when a turn is genuinely dropped mid-flight and how Omniscio notices and heals it.
• Session statuses — what the running state looks like in the sidebar, and every other state a session can be in.

The Escape key is a two-step guard. The first press only arms the interrupt and shows a hint; only a deliberate second press inside a short window actually interrupts, so a single stray or held key can never stop a running agent. The Stop button guards itself the same way: a rapid double-click sends one interrupt rather than two, and the button disables itself while the request is in flight so the click visibly acknowledges that something is happening.

Interrupt itself is provider-aware: the same gesture routes to whichever engine is running the session, so it works whether the session is on the standard Claude path or one of the alternative providers.

Related

• Send a message — the composer at the bottom of every open session.
• Queue a message — lining up a follow-up for when the agent finishes.
• Pause or stop a session — the four ways to stop, and which one you want.
• Keyboard shortcuts — the interrupt key and every other binding.
• Session statuses — the eleven states, including running.
• Aborted-response recovery — healing a turn that was dropped mid-flight.