Journal entry
journal_entryRecord a finished work chunk's outcome and summary in the agent journal, with status, next steps, and commit details; same-session audit entries are attached automatically.
Instructions
Write to the agent journal the outcome of a finished chunk of work. summary — 2-4 sentences: what and why. outcome — done/failed/partial/reverted. next — what is left (optional). commit — git hash, if the work produced a commit (optional). refs — arbitrary references (optional). The server itself attaches all audit entries of the SAME session since the previous journal entry of that same session (or since the start of the connection, if there was no entry yet) — there is no need to find and specify the range manually. If you are explicitly continuing an interrupted task from another (older) session, pass continuesFromSeq — seq of the last accounted audit entry, so its tail is not lost.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"summary": "<summary>",
"outcome": "<outcome>"
},
"name": "journal_entry"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | No | ||
| note | No | Short human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools. | |
| refs | No | ||
| agent | No | Short consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel. | |
| commit | No | ||
| outcome | Yes | ||
| summary | Yes | ||
| continuesFromSeq | No |