Happier Docs
Features

Steering & interrupting

Understand how Happier updates a busy lead session or a running execution run without losing your message.

Happier supports two related busy-send behaviors:

  • session steering for the main lead session, and
  • execution-run delivery modes for running subagents and delegate/review runs.

The shared goal is the same: let you send new context while something is already busy, without making you guess whether the message will be lost.

Session steering

Session steering means you send a new lead message while the main session is still in the middle of a turn.

When the current backend/runtime supports in-flight steering, Happier can inject the message into the active turn instead of forcing you to wait.

If steering is not available for that session/runtime, Happier falls back to the normal busy-send path for the main session.

Busy-session send policy

In the app, open:

  1. Settings
  2. Session
  3. Message sending
  4. When the agent is busy (steer-capable)

You can choose:

  • Steer immediately: send immediately and steer the active turn.
  • Server pending: store message in pending queue first.

Execution-run delivery modes

When the selected recipient is a running execution run, Happier shows a Delivery chip next to the composer.

The app currently exposes two modes:

Steer

This is the default for execution runs.

Behavior:

  • if the backend supports steering, Happier steers the active turn,
  • otherwise Happier aborts the current turn and immediately sends a new turn,
  • the run stays alive either way.

Interrupt

Behavior:

  • Happier always aborts the current turn,
  • then immediately sends your message as a new turn,
  • the run continues from there instead of being fully stopped.

Important distinction: interrupting a turn is not stopping a run

For execution runs, an interrupt changes the current turn.

It does not mean:

  • stop the whole run,
  • delete the run,
  • remove the run from history.

The run only leaves the available recipient list when it is no longer sendable, such as after stop/cancel, completion, or when a bounded run has already left its in-flight turn.

Interaction with pending queue and routing

Session steering and pending queue are complementary:

  • Use steering for quick context corrections while the turn is running.
  • Use pending queue when you want ordered, editable messages before execution.

Execution-run delivery is separate from that session-level pending behavior. For running execution runs, use the recipient and delivery chips documented here and in the participant-routing guide.

On this page