Create a lock
lock_createClaim a work item by writing an active lock file that lists your tasks, enabling conflict-free coordination across git worktrees without touching git history.
Instructions
Claims a piece of work by writing a new active lock file. Use this after you have decided to proceed (optionally having checked lock_query / lock_check_conflict first). tasks are created as a plain unchecked checklist; call lock_update as you complete each one. agent_id / parent_agent_id: pass your OWN id here only if you already know it from your own context (some orchestration harnesses hand a subagent an explicit id when dispatching it) — this server has no way to detect either value automatically (no MCP transport mechanism exposes a session/agent id to a stdio server subprocess). Omit them (or pass null) if you do not know them; they will be recorded as null, never fabricated. parent_agent_id specifically means "the id of whatever spawned you," if you are a subagent and happen to know it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | Glob patterns describing the files/paths this lock claims. | |
| tasks | Yes | Plain-text descriptions of the tasks you plan to do. All are created unchecked. | |
| title | Yes | Short human-readable title for this lock. | |
| agent_id | No | Your own agent id, ONLY if you already know it from your context. Omit or pass null otherwise — never guess. | |
| parent_agent_id | No | The id of whatever spawned you, ONLY if you already know it. Omit or pass null otherwise — never guess. |