Follow and continue a session
Read the transcript, respond to questions, inspect changes, and keep related work together.
A session keeps the conversation and related runs at one address. Starting a task creates its first run. Continuing completed or interrupted work can create another run without replacing the session.
Read the console
| Tab | Use it to |
|---|---|
| Transcript | Follow the agent's messages, commands, tool activity, and questions. |
| Review | Inspect captured changes and review conversations. |
| Runtime | Check the execution and model state exposed by the session. |
| Session | Read the session's details and related run information. |
The run indicator identifies the current run within the session. A temporary stream disconnection does not, by itself, mean execution stopped; check the run status before taking action.
Respond while work is running
Owners and admins can use the composer and available session actions. Answer a question with the missing fact or decision. For a correction, name the specific change needed and the expected behavior.
A submitted instruction is not proof that the agent has applied it. Follow the transcript and the resulting diff to confirm what happened.
Continue related work
Use Continue session or send a follow-up through the supported composer flow. The continuation keeps the session's identity and creates fresh execution when required.
From the terminal:
devboxes continue <session-id> "Add a regression test for the empty-value case."Use the session ID returned by dispatch, not a run ID. Keep the follow-up focused on the work already in that session.
Stop work carefully
Use the available stop action when you need execution to end. A stopping state means the request is still being processed. Stopping does not undo actions already taken in the repository or external services.
Inspect the final status and any preserved result before deciding whether to continue or start over.
Share the right information
Ordinary session links still require organization access. Where an integration provides a read-only share link, treat it as access to the information shown by that share and use the available revocation controls when access should end. Do not assume every private file or action is included.
See reviewing results for the distinction between execution, publication, and approval.