How It Works
A workflow that mirrors how developers already work.
Orient the repo, delegate the legwork, and keep authorship through review. The product gets out of the way without becoming vague.
01
Start in the workspace
Initialize Apsara inside the repo so the session inherits the right filesystem boundary and project-local context.
02
Ask for meaningful work
Trace the code, inspect files, and draft a change while keeping raw tool noise tucked away unless it is needed.
03
Review and steer
Approve the diff, reject it, or redirect the next step while the session keeps the thread and reasoning intact.