Skip to content
v3.2.22026-06-12

Multi-account switching and resume that hold up

BridgeSpace 3.2.2 makes multi-account agents dependable: switching Claude accounts keeps you signed in, resumes run under the account profile the conversation belongs to, and session recovery is honest about what can and can't be resumed.

  • Connected accounts stay signed in. Switching to a connected Claude account no longer re-runs the first-run wizard and its login screen — onboarding state is seeded from the CLI's real state file at connect and self-heals on every switch.
  • Resume follows the right account. Resuming a recovered agent now runs under the account profile the conversation was created on. Previously the resume used whichever profile was active, so Claude answered "No conversation found" after an account switch.
  • Home-directory agents are recoverable. Agents launched in a workspace rooted at the home folder were invisible to crash recovery — an empty Claude settings file silently blocked hook installation. They now register like any other agent and are offered for resume.
  • Resume failures speak up. When a resumed agent can't start — wrong account, missing CLI — BridgeSpace surfaces a notification and keeps the session recoverable under Settings → History instead of losing it.

Added

  • Agent sessions record the Claude/Codex account profile and transcript path they ran under, powering profile-aware resume.
  • Claude sessions register the moment the CLI starts (SessionStart hook), so an agent closed before its first reply is still offered for resume.
  • Agents launched from the workspace UI are recorded at spawn time, so Codex agents no longer wait for their first turn to become recoverable.

Changed

  • The launch-time cleanup of user-level Claude hook entries now skips workspaces rooted at the home folder, whose project settings live in the same file.

Fixed

  • Switching to a connected Claude account forced a re-login: the onboarding self-heal read .claude.json from inside ~/.claude, where the CLI never writes it — it now reads the real home-root state file, and connects seed it up front.
  • Resumed agents launched under whichever account profile was active and failed with "No conversation found" when it differed — resume commands are now pinned to the conversation's own profile.
  • A successful resume could be misread as failed when the replayed conversation contained phrases like "command not found", re-offering a duplicate resume — failure detection now stands down once the CLI demonstrably booted.
  • Resuming a conversation whose transcript was never saved (closed before the first reply) typed a command guaranteed to fail; it is now blocked up front with a notification and the dead entry stops being re-offered on every boot.
  • The default (un-profiled) Claude sign-in is now detected via its real Keychain item and state file, so Connect Accounts reports it accurately.
  • An empty ~/.claude/settings.local.json permanently blocked hook installation for home-rooted workspaces; empty files are now treated as a fresh install, and refusals are logged where builders can find them.
  • A failed resume silently consumed the session's recoverability; the session now returns to recoverable and a notification explains what happened.