v0.6.6
Bug Fixes
-
Chat API mounts propagation —
ChatAPIConfigandChatConfignow carryMounts, so caller-supplied volume mounts are stored in the chat record and forwarded toSpawnSession. Previously, mounts were silently dropped on JSON binding (#9). -
effectiveWorkDir skips volume-type mounts — Volume names (e.g.
persist-workspace-b4ce035a) are not filesystem paths and must not be stat-checked byValidateWorkDir.effectiveWorkDirnow ignores mounts withType: "volume"when deriving the working directory (#9). -
Chat config PATCH supports mounts —
PATCH /chats/:name/confignow merges themountsfield when provided.
What This Unblocks
With mounts flowing through the Chat API, external volume managers (like PERSIST's per-identity workspace volumes) can mount named volumes into chat sessions. Combined with the v0.6.5 resume pass-through, this enables end-to-end conversation continuity across session respawns.