worktree-session git:20260814.5313065A

Immutable. This exact content never changes and is served at /api/v1/blob/1dc3ea6f4e67e5ba.

---
name: worktree-session
description: The worktree is the isolation boundary when many agents edit one repo — your own branch, declared files, reconcile before building, never destroy work that is not yours, cleanup. Use at the start of and throughout any assignment that touches a repository.
---

# Worktree session

Other agents edit the same repository at the same time. The worktree is the isolation
boundary.

1. Work in a worktree that is yours to write whenever the project is in a git repo: by
   default one you create at the start of the assignment, **inside your own workdir**
   (`<workdir>/<branch-name>/`), on a branch named for the work; or one the assigning
   agent hands you for the job (an orchestrator passing a worktree down to you). Either
   way it lives in a durable assignment workdir — never system temp or your home.
2. A repo below your session root does not announce its conventions: its `AGENTS.md`
   and committed skills do not load into your session. Read them when you enter it.
3. Treat an assignment's `--files '["path", ...]'` list as optional bootstrap context.
   It names likely starting paths; it is not custody, authorization, or a complete source
   boundary. Read and edit every path the assigned work needs. If current source inspection
   shows that another holder is changing the same code, report the real collision truthfully
   and coordinate the order or reconciliation before both changes proceed.
4. Destructive git that hides or discards another agent's uncommitted work is refused
   at the gate before it runs — `git stash` (mutating forms), `git reset --hard`,
   forced `git clean`, `git checkout -- <path>`, and `git restore` all hit a refusal
   with the reason attached. Do not route around a refusal; it is protecting a
   colleague's work. To undo your OWN uncommitted edit, reverse the edit itself — the
   same tree can hold work that is not yours.
5. A dirty tree or mid-flight branch that is not yours is not yours to reset, restore,
   or clean — and it is also not a blocker to stall on. Reconcile it: identify who or
   what created it (`git log`, the branch name, `tightbeam list` for the sessions
   around you), then either wake the owner to clean it up, or remove it yourself once
   you have established it is safe (abandoned, yours, or the owner agrees).
6. Reconcile main into your branch before building on it: merge main in, resolve
   conflicts on your branch, and prove the combined result builds and passes tests
   there. Do not build new work on a branch that has diverged from main.
7. After your branch merges, prune your worktree and delete the merged branch. A
   finished assignment leaves no worktree behind; attest the cleanup as part of
   completion.