The new Continue adapter (src/retitle/adapters/continue_dev.py) was added in v0.5.0 based on the public knowledge that Continue stores sessions as JSON files at ~/.continue/sessions/<id>.json. The schema assumed:
{
"sessionId": "...",
"title": "...",
"workspaceDirectory": "...",
"history": [
{ "message": { "role": "user", "content": "..." } },
{ "message": { "role": "assistant", "content": "..." } }
]
}Looking for someone who actively uses Continue to validate this. Specifically:
- Does the path still resolve correctly with the current Continue extension (continue.dev)? VS Code and JetBrains versions both?
- Is the title field actually called
title in your JSON?
- Are messages structured under
history[*].message with role + content?
- After
retitle once --tool continue --session <id>, does the new title actually show up in the Continue sidebar after a restart? Or does Continue ignore on-disk changes?
A redacted dump of one session JSON (with text content scrubbed) would be enormously helpful. Or just a jq 'keys' of the top-level keys + the same for .history[0].
PR welcome.
The new Continue adapter (
src/retitle/adapters/continue_dev.py) was added in v0.5.0 based on the public knowledge that Continue stores sessions as JSON files at~/.continue/sessions/<id>.json. The schema assumed:{ "sessionId": "...", "title": "...", "workspaceDirectory": "...", "history": [ { "message": { "role": "user", "content": "..." } }, { "message": { "role": "assistant", "content": "..." } } ] }Looking for someone who actively uses Continue to validate this. Specifically:
titlein your JSON?history[*].messagewithrole+content?retitle once --tool continue --session <id>, does the new title actually show up in the Continue sidebar after a restart? Or does Continue ignore on-disk changes?A redacted dump of one session JSON (with text content scrubbed) would be enormously helpful. Or just a
jq 'keys'of the top-level keys + the same for.history[0].PR welcome.