Foreman v1.1.2
Your own memories show up on the canvas again
A memory you saved from the chat didn't appear on the canvas — not until the next time you restarted the app, because the canvas read each machine's memory list once and then held it. It updates as you save now, and as you rename or delete from the Memories tab. Memories saved from an isolated worktree session were worse off: they were filed under the throwaway checkout the session was working in, so they belonged to no project on the canvas at all and turned up under a session-… heading in the Memories tab. They're filed under the project itself now, wherever the session happened to be running. Memories saved before this update keep the path they were stamped with.
Delete a memory Claude wrote
Claude's own memory files were read-only in Foreman — you could open one from the canvas and read it, but clearing out a stale note meant going and finding the file yourself. They can be deleted now, from the same dialog, and the pointer to the deleted note is stripped from the project's MEMORY.md index so Claude stops being told about a file that no longer exists. Deleting any memory — Claude's or your own — now asks first, since there's no undo. If a save or delete does fail, the dialog keeps your file and its buttons on screen instead of replacing them with the error, so you can just try again.
Git errors read like a status line, not a crash
The Git page printed raw git output in full red text, so an ordinary refusal — checking out a branch another worktree already has, say — filled the panel with four wrapped lines and looked like something had broken. Those messages are now a single truncated line, with the whole text on hover if you need it. The same treatment covers the branch, push, merge and commit panels, matching how the diff view has always shown a failed commit.
The dot follows background work to the end
A session that dispatched background work — a workflow, or an agent sent off to run on its own — changed status when that work finished, but never raised the dot that tells you a session wants you. The turn itself had ended long before, so the "finished" signal had already come and gone. Finished background work now lights the same dot and adds the session to your inbox, so it's visible from the list and the canvas rather than only in a desktop notification you may have missed. A turn that failed keeps its red dot: later background work completing won't paint over the fact that something went wrong.
macOS, Apple Silicon. Signed with a Developer ID certificate and notarized by Apple — opens normally with no Gatekeeper warning, and in-app silent auto-update is enabled.