Use Cases
Outcome-oriented Compozy operating paths for code review, release readiness, and agent handoff.
Use cases start from an operator goal, then connect the runtime pieces that make that goal repeatable. They are intentionally less exhaustive than reference pages and more concrete than concept pages.
Prepare a project workspace
Register a repository, add a workspace-local agent, write the first memory, and prove the session can see the right root.
Review a change
Run an agent against a workspace, ask for review evidence, and follow the session until it produces usable feedback.
Run a release sweep
Turn release checks into task runs with attached sessions, durable status, and explicit completion evidence.
Hand off between agents
Use Compozy Network channels to request work, receive messages, and close the loop with receipts and traces.
How to read these pages
Each use case follows the same shape:
| Section | Purpose |
|---|---|
| Setup | The minimum runtime state needed before the flow starts. |
| Flow | The sequence of CLI, API, or file actions an operator or agent can repeat. |
| Evidence | The status, events, or history that prove the flow really happened. |
| Failure path | The first place to look when the flow stalls or produces unclear output. |
Use Guides when you need to choose a surface or debug a session. Use Runtime Overview when you need the underlying runtime model.