Save Context Tool
save_contextSaves a project’s approved Markdown context document as a first or new version, preserving concurrent updates and excluding secrets.
Instructions
Saves the project's context document: the first version (base_version 0) or a new one (base_version = the version you read with project_context). Only after the person saw the text and said yes. Never secrets. If a colleague saved a newer version meanwhile, nothing is overwritten.
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": {
"body": "<body>",
"base_version": "<base_version>"
},
"name": "save_context"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The whole context, in Markdown (not only the changed part). | |
| note | No | What changed, in a few words (e.g. "added how to deploy"). | |
| repo | No | The output of git remote -v in the working directory. | |
| agent | No | The agent writing this: claude-code, codex, cursor. | |
| project | No | Project slug or name, when there is no repo or session project. | |
| session | No | This session's id, from the cemainou line at the start of the session. The session's project wins over the repo. | |
| base_version | Yes | 0 for the first version; otherwise the version you read with project_context. |