How to

Claim implementation

Assign implementation and record the confirmed branch before edits begin.

What changes

claim records who is implementing the approved plan, plus the current branch and source commit. Flows with a human or ask-style branch check require explicit --confirm-branch approval.

When this helps

The plan is approved and an implementation session is about to edit files.
A delivery lead needs to see which session owns the work.
A handoff should preserve implementation ownership.

Run this command

terminal

$sumr mission claim SUM-123 --agent codex --workspace-owner user --confirm-branch# claim on the reviewed branch

Flags you can use

--agent <name>

Name the person, AI assistant, or session claiming work.

--confirm-branch

Record explicit approval of the current branch when the flow requires it.

--workspace-owner <owner>

Set explicit ownership to user, mission, platform, or external.

--allow-custom-key

Accept a work key that does not match a configured work-provider prefix. Use only for local or intentionally custom work.

--json

Return a structured JSON envelope for scripts, CI jobs, and AI assistants.

--help, -h

Show the command syntax, supported flags, and examples without changing files.

Keep in mind

Claiming always requires an accepted plan.
Workspace ownership is explicit and is never inferred from the checkout path or worktree shape.
When the configured branch-check step advances automatically, --confirm-branch is not required.