SingulaComp does work inside a session: a branch and a sandbox for one unit of work. A session ends when its change request (CR) merges back to the default branch. This page walks through the loop, then shows the three ways a session can start.

What happens when a session starts

SingulaComp creates the session row and cuts a branch from the default branch. The branch name is the session id.
SingulaComp resolves a sandbox image: the default image, or your own .singulacomp/Dockerfile if the manifest declares one.
The sandbox boots. Its daemon, singulacomp-agent, clones the repo to /workspace. It starts OpenCode REST. Session status becomes running.
The agent works. It uses secrets through the environment variables SingulaComp sets, then commits and pushes to the session branch.
The agent opens a change request. You review it and merge it — the only way work reaches the default branch.

Git is the only durable record

Stopping a session pauses the sandbox but keeps its files. Deleting a session destroys the sandbox for good. Only work committed and pushed to the branch survives, and only a merged change request makes it permanent.

Three ways work runs

A session starts one of three ways.

Mode	How it works
On-demand	You ask in chat and get the result now.
Human-assisted	The agent works and checks in with you for the calls that matter.
Automated	A trigger — a schedule or webhook — starts the session end to end.