Skip to main content

​
Enable Team mode

Team mode does not implicitly claim or release features. Before subsequent write operations such as verify, run feature start or claim so the caller holds a valid claim.

​
owner and actor

  • owner identifies the person ultimately responsible, such as a developer or team member.
  • actor identifies a particular Agent session, such as codex-1.
  • Multiple Agent sessions can share the same owner and use distinct actor IDs, but each feature can have only one claim.
See the claim options →

​
Leases

Renew long-running work before its lease expires:
See the claim renew options → A takeover is allowed only after the lease expires:
See the expired-takeover options → The takeover preserves the previous owner information for auditing. An active lease cannot be forcibly overwritten.

​
WIP limit

feature_list.json.rules.wip_limit_per_owner defaults to 1. After reaching the limit, an owner cannot claim another feature. Complete, block, or release the current feature instead of bypassing the limit with a new owner name.

​
Claim the next feature

See the claim --next options → The command selects only a not_started feature with no valid claim and with all dependencies in passing. Lower priority values take precedence.

​
Cross-machine synchronization

See the claim --push options → --push commits to origin/main by default. Use --remote and --branch to change the target. Two devices can still claim the same feature locally at the same time. If a push conflicts, the tool synchronizes with the remote and attempts to fall back to the next ready feature.

​
Independent workspaces

Options: Create a workspace · View workspaces The workspace is located at .worktrees/<feature-id>, and its branch is feature/<id>. The status command shows both whether the claim is active and whether the path still exists. Remove it after completing and pushing the work:
Options: Remove a workspace · Prune workspaces remove refuses a dirty or unpushed workspace. prune removes only safe items whose claims have been released or expired; it never removes a workspace with an active claim.
  1. Every Agent synchronizes with the remote and reads status.
  2. Each Agent claims a different feature and creates its corresponding workspace.
  3. Renew leases as needed, and run feature block immediately when blocked.
  4. A reviewer with a different owner identity records the review.
  5. After completion, push the code and state, run session close, and then clean up the workspace.
A Git claim is an auditable collaboration protocol, not a real-time distributed lock. Cross-machine work must synchronize with the remote and cannot rely only on the local feature_list.json.