v0.41.8

Memories: the same request always gets the same memory, a shared memory keeps finished tasks either way, and the list refreshes; the runner works in a session's files only as that session (0.41.8).

Memories

• New setup gets the same memory for the same request. The memory an agent gets was chosen from words Studio's builder writes afresh each time (the agent's name, instructions and hint), so the same request could get a shared Graphiti memory once and a per-person one the next time. The person's own goal, as typed, is now read first: when it says clearly what the agent should remember, it decides, for the setup card and the save alike. Otherwise nothing changes.
• Sharing a memory keeps finished tasks whichever switch you press first. Switching a memory On for an agent that has nowhere else to write makes it where the agent writes. Now the agent's finished tasks are kept there too, the same as when its own memory is switched Off afterwards. An agent that uses a memory remembers its work in it.
• The Memories page shows a memory made meanwhile (say, by a setup you just built in another tab) when you come back to it, without a reload.

Runner

• The checkpoint reads a session's folder as that session, as restoring it already wrote as it. A file the session made unreadable to itself is left out of the checkpoint and named in the log, never its contents.
• An environment's built layer is made read-only by a walk that never follows a link, and a file with several names the build doesn't own is taken out of the layer.
• A turn's terminal folder is removed only when it is exactly the one the turn made, and as the session that made it. The workspace history rewrite removes its scratch file as the session.
• The model probes for jcode and fast-agent start from folders of their own.
• With a user per session, the runner starts only with its marker folder on the volume (HR_WS_MARKER_DIR, root's, mode 0700), as the entrypoint sets it, rather than falling back to /tmp.
• A remote backend's record is logged by name and size, never its contents.
• The entrypoint says once when the host lets one user hard-link another user's file (fs.protected_hardlinks=0), and the self-hosting guide shows how to set it to 1.

Checked: gateway, runner, console and integration suites; the new tests fail on 0.41.7. On the release candidate: Claude Code, Codex, OpenCode and Hermes each passed a first turn, a follow-up, a model switch, a file produced and a recycle (the session restored from its checkpoint and still remembering); the same request built twice in Studio got the same memory; switching a memory on after the agent's own was off kept its finished tasks.

Full Changelog: v0.41.7...v0.41.8