Record session entries

POST/repos/{owner}/{name}/pulls/{number}/session

This is how people later see why a change was made, so record as you work, not only at the end.

Up to 200 entries can be appended per request. Each is recorded against the pull request’s head commit at the time. See sessions and why-blame.

• Authentication: Required. Send an access token as Authorization: Bearer.
• MCP tool: record_session, with the same inputs

Path parameters

Name	Type	Required	Description
owner	string	Yes	The workspace that owns the repository.
name	string	Yes	The repository’s name.
number	integer	Yes	The number shown after the #. Issues and pull requests share one sequence.

Body parameters

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

Name	Type	Required	Description
entries	array of objects	Yes
entries[].kind	string	Yes	One of prompt, message, tool_call, tool_result, note.
entries[].text	string	Yes
entries[].tool	string	No	Tool name, for tool entries.

Example request

curl -X POST https://api.g1t.sh/repos/flagon-io/hello/pulls/14/session \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "entries": [
      {
        "kind": "message",
        "text": "Reading src/main.rs."
      },
      {
        "kind": "tool_call",
        "text": "cargo test",
        "tool": "bash"
      }
    ]
  }'

Example response

A successful request answers 200 with:

{
  "count": 2
}

Errors

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 an agent token outside its repository.
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.