Interrupt, stop, resume

A session has three lifecycle controls. Each does something different.

Interrupt

Interrupt cancels whatever turn the agent is in the middle of. The subprocess stays alive; no new tool calls or messages from this turn are produced.

When to interrupt:

• The agent is heading in the wrong direction and you want to redirect before it finishes the current task.
• You want to take over with your own next message instead of letting the current turn run to completion.

Click Interrupt in the session header. The agent stops the current turn. The composer stays open so you can type your next message.

Stop

Stop ends the session. The agent subprocess terminates; no further work is possible in that session.

Stopped sessions stay in your sidebar with the full transcript. You can re-open one to read it any time. Stop is the right choice when:

• The task is done.
• You want to free up the subprocess (each running agent uses some memory).
• You want a clean conversation history for a new direction.

Click Stop in the session header. The status dot turns gray.

Resume

Resuming means continuing the same conversation. Some agents support this natively (Claude Code does, with the same session id). Others fall back to a fresh subprocess that’s seeded with the previous transcript.

To resume:

1. Click the stopped session in the sidebar.
2. Type your follow-up message in the composer.
3. Press Enter.

Glueprint figures out whether the underlying agent can re-attach to the previous conversation; if it can, it does. If it can’t, it spawns a fresh process and gives the agent the prior conversation as context.

On the portal

The portal exposes the same Interrupt and Stop controls in the session header. Stopping or resuming from the portal triggers the action on the host where the session lives; you’ll see the state change there too.

On mobile

Tap Interrupt, Stop, or Resume in the session detail header. Same semantics. Some long-running approvals are easier to handle on a phone, so interrupting-from-mobile is a common pattern.

From the CLI

On a CLI daemon host, list sessions and stop one by id with the session subcommands (see CLI Daemon). Starting and resuming sessions from the CLI directly is not supported today — drive the host from the portal or mobile.

What happens to files?

Interrupting or stopping doesn’t change files on disk. If the agent edited files during the session, those edits stay. If you interrupted mid-tool-call, the call is canceled but any side effects already done (a written file, a shell command run) are not rolled back.

Related topics

• Start a session
• Search and filter
• Assistant chat for spawning sessions from a chat message instead of the new-session composer.