Under the hood
Useful2 Signal3
Plugin, MCP, resume and worktree paths now take an explicit storage handle, changing where state lives.
What's wrong with this entry?
Anonymous. No account, no email.
What
Settings writes, the plugin enable, disable, install, prune and uninstall commands, MCP client setup and reconnect, agent and skill loading, session resume, transcript reads, worktree metadata and background process spawn all now take an explicit storage handle, which changes where that state is read and written from.
Details
- On Windows, the daemon's terminal process-id files are read and deleted through storage keys in a
pty-pidsnamespace rather than direct filesystem paths, when a handle is available.
Evidence
pty-pids
Strings lifted out of the shipped bundle, so the claim above can be checked against them.