capcom lock

capcom lock

Acquire, refresh, release and inspect this worktree’s Tree lock

Synopsis

Manage this worktree’s Tree lock: the advisory claim one agent session holds on one working tree while it edits. acquire claims it and prints a Lock token, touch renews its heartbeat with that token, and release frees it. A lock whose heartbeat is older than the TTL (lock.ttl in config.yaml, two hours by default) is stale: it stays held until its holder resumes it, another session takes it over with acquire –take-stale, or someone breaks it. Each git worktree has a lock of its own, and capcom installs no git hooks: the lock binds only the sessions that check it.

capcom lock [flags]

Examples

  capcom lock acquire --purpose "implementing the release plan"   # prints the token to keep
  capcom lock touch --token <token>     # renew the heartbeat
  capcom lock status --all              # every worktree's lock
  capcom lock release --token <token>   # free it when the work is done

Options

  -h, --help   help for lock

Options inherited from parent commands

      --json   print a versioned JSON envelope

SEE ALSO

• capcom - A git-native issue tracker and knowledge store for coding agents
• capcom lock acquire - Acquire this worktree’s lock, or resume it with your own token
• capcom lock break - Free this worktree’s lock whoever holds it
• capcom lock check - Exit 0 when this worktree’s lock is free or yours, 3 when another holds it
• capcom lock release - Release the lock you hold; releasing a free lock does nothing
• capcom lock status - Show this worktree’s lock, or with –all every worktree’s
• capcom lock touch - Refresh the heartbeat of the lock you hold