save_session
Persist decisions, context, and plans across coding sessions by saving key-value entries to named sessions. Keys update in place if they already exist.
Instructions
Save a key-value entry to a named session. Use to persist decisions, context, plans, and findings between coding sessions. Each session can hold multiple keys (e.g., 'summary', 'active_tasks', 'decisions'). Keys are updated in place if they already exist.
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": {
"session": "<session>",
"key": "<key>",
"value": "<value>"
},
"name": "save_session"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes | Session name (e.g., 'admin-crowlr-upgrade', 'compr-app-v2'). Will be created if it doesn't exist. | |
| key | Yes | Entry key within the session (e.g., 'summary', 'active_tasks', 'decisions', 'blockers') | |
| value | Yes | Content to save — can be a summary, list of tasks, decisions, notes, code snippets, etc. |