v0.6.9
Bug Fix
- Resume across chat sessions — When
PersistSession=true, the Docker runtime added a per-session volume at/home/agent/.claude/projects. But the chat manager already mounts its own per-chat volume at the same path. Docker uses the last-vflag, so the per-session volume (fresh, empty) shadowed the chat volume (which holds JSONL from prior sessions).--resumepassed the correct session ID but Claude couldn't find the JSONL file. Fixed by skipping the auto-created PersistSession volume when a volume mount already exists at the target container path. (#8)
Complete Fix Chain (v0.6.6–v0.6.9)
| Version | Fix |
|---|---|
| v0.6.6 | Mounts + effectiveWorkDir propagation through Chat API |
| v0.6.7 | Volume permission init (chown to agent user) |
| v0.6.8 | Claude/Codex config propagation (claude_md, settings) |
| v0.6.9 | Prevent per-session volume from shadowing chat volume |
All four issues shared a common theme: the Chat API was a thin passthrough that didn't account for the Docker runtime's volume lifecycle. With v0.6.9, the full per-user workspace feature should work end-to-end: volumes mount, permissions set, Claude reads instructions, and resume finds prior session history.