Product
Industries
Roles
Research
Resources

Live runs

An agent has spent forty minutes on the wrong branch, and the only way to stop it is the terminal on someone else's laptop. Live runs list what waits on you, let you send a correction to a run in flight, and show whether the agent received it.

    An example run replay. Follow its transcript, work, tasks, changes, subagents, and cost, with controls to pause, seek, and change speed.

    Runs that need you

    One list holds what waits on you in the workspace: approvals and questions on your runs, work waiting in review, and steering suggestions. It is ordered by how many agents each item blocks, then by age.

    A pending approval is a tool call a rule held for a person. A question is an agent that paused to ask one. Each shows the run, its agent, and its operator, the person accountable for that run, and the soonest expiry comes first.

    The Runs page on a phone, with illustrative data. It shows 20 live runs, the runs waiting on you, and today's spend, then each run as a card under Live, Parked, and Ended.

    The Runs page on a phone

    Send a correction

    Change direction while the work is happening. Open a run and send a correction. Oxagen delivers it at the agent's next turn, before its next step where the host supports that, or by cutting the model call in flight on runs whose model traffic passes through Oxagen. The record shows whether the steer is still waiting or has reached the agent.

    A steer goes to one run, to every live run of one agent, or to every live run in the workspace. A steer to an agent with no run in flight waits for its next run. A workspace can cap the text one run receives this way.

    A live run's page with illustrative data, in the conversation style. The person's prompt opens the transcript, and the agent's replies follow with one line for each step between them.

    A live run in the conversation style

    Delivery modes by harness

    The strongest mode each wrapped harness receives
    HarnessAt the next turnBefore the next stepInterrupt a model call
    Claude CodeYesPartialWhen the host advertises step deliveryPartialWhen the run's model calls go through Oxagen's local proxy
    CodexYesPartialWhen the host advertises step deliveryPartialWhen the run's model calls go through Oxagen's local proxy
    StellaYesPartialWhen the host advertises step deliveryPartialWhen the run's model calls go through Oxagen's local proxy
    CursorYesNoIts hook delivers at the end of a turnNoIts model calls do not pass through the proxy

    Delivery status

    See whether your steering reached the run. When a run cannot take the mode you asked for, Oxagen records both the mode you asked for and the mode it will use, with the reason. A steer that cannot move earlier waits for the next turn, because cutting a call without delivering the text would disrupt the run and steer nothing.

    Each steer moves through its own states: queued, sent, received, acknowledged, and applied. It can also end cancelled, expired, or failed, with the reason. Queued means Oxagen holds it. Applied means the recorder placed it in front of the agent and wrote that into the run's record.

    A run's transcript with illustrative data, in the standard style. Each row is tagged Model, Tool, Governance, Context, or Operator, so a person's message reads as its own row beside the agent's calls.

    Each transcript row tagged with its kind

    Run controls

    In scope

    • Pause, resume, cancel, steer, and message for runs wrapped by the oxagen recorder
    • One run, every live run of an agent, or every live run in the workspace
    • A reason the agent reads when it resumes after a pause

    Out of scope

    • Runs that are not wrapped by the recorder
    • A run whose host is missing, revoked, or silent, which records the steer as failed
    • A guarantee that the agent follows the text it received

    Product walkthrough

    Review a supported live run and follow a correction to delivery.