Repository navigation
-
The side-panel email composer no longer offers to send — the panel an agent opens beside its tab is for you to review and edit the draft, and that is all it does now. Its built-in prepare and send actions, which could never work because Clave holds no Gmail credentials and which kept sending agents down a path that ended on a configuration error, are gone, with the delivery line in the composer's foot and the Nodemailer dependency. The agent reads the reviewed email back and sends it through its own channel (its mail tool or script); the read now names each attachment's file path so the agent can attach the retained copy. An email saved by an earlier version still opens; its old delivery fields are dropped (PRDCT-3438).
-
An app attached to the separate server comes back as it was left — a quit and a relaunch of an app attached to a Clave server running on its own show the same groups with the same members (the layout merge keeps a group's members until the server has said which exist, instead of pruning them before the server's records arrive and writing the flattened layout back), offer the sessions that ended for relaunch and bring the toolbar terminals back, as inside the app; a tab brought back while its agent works shows the working state at once, instead of idle until the agent's next word, in both modes; and a sidebar update that lost its cause on the way (the catch-up read after a reconnect, a save refused while a push was held) takes a tab or a terminal in without selecting it. Five end-to-end specs that ran against the in-process server alone run in both modes, and two new ones pin the restore and the state in both; the specs that keep their pin name the task their attached gap belongs to. In the app as shipped, the one visible change is the working state shown at once on a tab brought back after a quit.
-
An app attached to the separate server brings back and moves its sessions — on an app attached to a Clave server running on its own, the sessions left open come back after a quit (the records are the server's: a window that had sessions reads them off the server once the boot is done, each window taking its own and the primary the orphans), a tab or a group moves between windows and a closing window hands its sessions to the primary (the session is released on the server, which owns the process, and the window's layout follows), and a Claude tab the server starts reaches Clave's agent tools (the shell announces its MCP address to the server, the server writes the tab's config and mints its token, and the shell resolves that token through the server on every call). Groups whose members all live on the server are not yet rebuilt after an attached quit, which is named for the next wave. Nothing changes on screen in the app as shipped.