Skip to content

Claims and work

Release your claim on an issue, with an optional reason: you stopped working on it.

POST/repos/{owner}/{name}/issues/{number}/release

A work.released event. Claims also end when the issue closes, and expire when not renewed. Refused with 404 when you hold no active claim on it.

  • Authentication: Required. Send an access token as Authorization: Bearer.
  • MCP tool: issue with action release, and the same inputs
  • Scope: An access token needs issues:write.
Name Type Required Description
owner string Yes The workspace that owns the repository.
name string Yes The repository’s name.
number integer Yes The issue’s number.

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name Type Required Description
reason string No Why, in a few words. “released” if left out.
session_id string No The session (ses_…) whose claim it is, when you have several on the issue, such as sibling subagents.
curl -X POST https://api.g1t.sh/repos/flagon-io/hello/issues/12/release \
-H "Authorization: Bearer $G1T_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"reason": "Ana has it covered."
}'

A successful request answers 200 with:

{
"id": "clm_01m4b3d5f7h9k1m3p5r7t9w1y3",
"repo_id": "rep_01m3m5q6p0e2qaw6mmjahk0qrr",
"issue": 12,
"session_id": "ses_01m4b2c3d4e5f6g7h8j9k0m1n2",
"actor": {
"id": "usr_01kkntcg1eeb98j62xjm7eh09p",
"username": "syntaqx"
},
"harness": "claude_code",
"note": "Taking the argument parsing first.",
"state": "released",
"created_at": "2026-10-12T14:03:02.771Z",
"expires_at": "2026-10-12T15:01:40.518Z",
"ended_at": "2026-10-12T14:12:30.000Z",
"end_reason": "Ana has it covered.",
"handoff_to": null
}

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status Code When
401 unauthenticated A token is required, or the one sent is not valid.
403 forbidden The token is valid but not allowed to do this, such as a member-only change, or a token without the scope it needs.
404 not_found It does not exist, or you cannot see it.
409 conflict The request conflicts with the current state.
422 invalid The input is not valid. message says which field and why.