Review a Change
Use a Compozy session to inspect a code change and return durable review evidence.
- Audience
- Operators running durable agent work
- Focus
- Use Cases guidance shaped for scanability, day-two clarity, and operator context.
This flow is for a maintainer who wants a review that can be inspected after the terminal closes. The agent can run locally or inside a configured sandbox; the important part is that Compozy owns the session, events, and history.
Setup
Register the repository once:
compozy workspace add /Users/you/project --name projectIf the review should run away from the host filesystem, attach a sandbox profile:
compozy workspace edit project --sandbox daytona-devFlow
Start a named session
Create a session in the registered workspace so every later command can reference one durable session id.
Ask for bounded review evidence
Give the agent the files, branch, or diff boundary and ask for findings with file references, reproduction notes, and residual risk.
Watch the event stream
Follow events while the agent reads files, calls tools, and produces output.
Read the final history
Use history after the run to see the same turns without relying on terminal scrollback.
compozy session new --workspace project --agent reviewer --name review-checkout -o json
compozy session prompt sess_1234 "Review the current change. Return only actionable findings with file paths and evidence."
compozy session events sess_1234 --follow
compozy session history sess_1234Evidence to keep
| Evidence | Command | Why it matters |
|---|---|---|
| Session identity and status | compozy session status sess_1234 -o json | Shows workspace, agent, status, failure, and sandbox metadata. |
| Tool and model activity | compozy session events sess_1234 --last 50 | Shows whether the agent actually inspected the right surfaces. |
| Review output by turn | compozy session history sess_1234 | Gives a durable transcript to paste into a PR or release note. |
| Remote execution, if enabled | compozy session status sess_1234 -o json | The sandbox object proves which backend and profile were used. |
Failure path
| Symptom | First check | Next page |
|---|---|---|
| Agent reviewed the wrong tree | compozy workspace info project -o json | Workspace Resolution |
| Session has no useful events | compozy session events sess_1234 --last 50 -o json | Event Streaming |
| Sandbox did not attach | compozy session status sess_1234 -o json | Sandbox |
| Follow-up prompt does not move | compozy session status sess_1234 -o json | Debug a Failed Session |
When to use tasks instead
Use a plain session for one review. Use task runs when review work needs assignment, leases, retry visibility, or completion records that other agents can claim.