# Live coding agent direction | Oxagen

Source: https://oxagen.sh/product/runs/live

# 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.

[Follow work from its source to its outcome](https://oxagen.sh/#demo)[Read the product overview](https://oxagen.sh/product)

A release agent's run still in flight. A rule routed its push to Sam Chen, who approved it three minutes later. Priya Shah sent a correction, which reached the agent at its next turn, and the agent is now editing the release notes. It has cost $0.66 so far.

One live run

**Cut the 4.11.0 release notes**Release agent run by Priya ShahRunning**$0.66**Cost so far

1.  09:12**Run started on Claude Code**Mandate release. Operator Priya Shah.
2.  09:14**Read 22 files and 31 merged pull requests**Allowed by rule repo.read+$0.62
3.  09:21**Asked to push to release/4.11**Routed to Sam Chen by rule release-branch+$0.04
4.  09:24**Sam Chen approved the push**Answered in 3 minutes
5.  09:25**Priya Shah sent a correction**Reached the agent at its next turn
6.  09:26**Editing docs/releases/v4.11.0.mdx**Allowed by rule docs.write

Illustrative A run in flight with its correction delivered

01

## 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.

02

## 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.

03

## Delivery modes by harness

The strongest mode each wrapped harness receives
| Harness | At the next turn | Before the next step | Interrupt a model call |
| --- | --- | --- | --- |
| Claude Code | Yes | PartialWhen the host advertises step delivery | PartialWhen the run's model calls go through Oxagen's local proxy |
| Codex | Yes | PartialWhen the host advertises step delivery | PartialWhen the run's model calls go through Oxagen's local proxy |
| Stella | Yes | PartialWhen the host advertises step delivery | PartialWhen the run's model calls go through Oxagen's local proxy |
| Cursor | Yes | NoIts hook delivers at the end of a turn | NoIts model calls do not pass through the proxy |

04

## 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 steer asked for an interrupt and was recorded as before the next step, because the run's model calls do not pass through the proxy. It was queued, sent, and received, and is not yet applied.

One steer on its way to a run

1.  QueuedReachedRecorded as before the next step
2.  SentReached
3.  ReceivedReached
4.  AcknowledgedPending
5.  AppliedPendingIn the agent's context and on the run's record

Illustrative Command states from the recorder's wire format

05

## 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

## Related pages

*   [
    
    ### Runs
    
    The record each agent run leaves
    
    ](https://oxagen.sh/product/runs)
*   [
    
    ### Budgets and stops
    
    Spend ceilings and run stops
    
    ](https://oxagen.sh/product/mandates/budgets)
*   [
    
    ### Developers
    
    Wrap the agent you already use
    
    ](https://oxagen.sh/roles/developers)

## Product walkthrough

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

[Follow work from its source to its outcome](https://oxagen.sh/#demo)[Read the product overview](https://oxagen.sh/product)