The new Zed adapter (src/retitle/adapters/zed.py) was added in v0.5.0 with a best-guess at the Zed Assistant storage layout. Stored conversations:
- macOS:
~/Library/Application Support/Zed/conversations/<uuid>.json
- Linux:
~/.config/Zed/conversations/<uuid>.json
We assumed:
{
"summary": "auto-generated title",
"messages": [{ "role": "user", "text": "..." }, { "role": "assistant", "text": "..." }],
"project": { "path": "/path/to/cwd" }
}
Need a Zed user to validate. Specifically:
- Does the path still resolve in the current Zed (Zed v0.16+ may have moved storage; some flavours use SQLite-backed threads now)
- Is the title field really called
summary? If not, what?
- Are messages
messages[*].role + messages[*].text? Or some other shape?
- Does Zed reload from disk on next launch if we rewrite the title? Or does it cache and overwrite?
A redacted top-level jq 'keys' of one conversation file is enough to start. PRs welcome.
The new Zed adapter (
src/retitle/adapters/zed.py) was added in v0.5.0 with a best-guess at the Zed Assistant storage layout. Stored conversations:~/Library/Application Support/Zed/conversations/<uuid>.json~/.config/Zed/conversations/<uuid>.jsonWe assumed:
{ "summary": "auto-generated title", "messages": [{ "role": "user", "text": "..." }, { "role": "assistant", "text": "..." }], "project": { "path": "/path/to/cwd" } }Need a Zed user to validate. Specifically:
summary? If not, what?messages[*].role+messages[*].text? Or some other shape?A redacted top-level
jq 'keys'of one conversation file is enough to start. PRs welcome.