worktreelisted

# UZE — working in an isolated checkout You do not decide whether to work in isolation, and you do not create your own top-level worktree. UZE places every agent it launches in a checkout of its own under `.worktrees/<id>`, on branch `agent/<id>`, before you start. The primary checkout belongs to the operator. Read the "Concurrent work isolation" section of `AGENTS.md` — it states the layout and what happens to finished work. This skill is what no harness does for you: the part of that arrangement you have to carry yourself. ## Know where you are ```bash git rev-parse --show-toplevel git branch --show-current git status --short ``` If your working directory is inside `.worktrees/`, you are already isolated: work here, commit here, and do not create another worktree or switch branches. If you find yourself in the primary checkout, you were started by hand rather than by UZE; the operator's uncommitted work there is theirs — never stash, reset, clean, or move it. ## Commit on your branch, and stop there Commit your work on your own branch as you go, in focused commits that each pass the project's checks. Never commit to, merge into, rebase, or reset the target branch: delivery is UZE's. When you are done, leave a clean tree — uncommitted work is reported to the operator as exactly that, and is not delivered — and end your turn. What happens next is the project's declared completion behavior, and it is not yours to perform. ## When UZE hands work back to you UZE rebases