changexbc/workbuddy-switch

A niche utility that is worth trying only if you juggle several WorkBuddy or CodeBuddy accounts and are tired of logging out and back in by hand. Its value comes from wrapping account switching, session migration and usage monitoring in one Tauri desktop app.

The problem

Someone with a personal and a team WorkBuddy account, plus CodeBuddy IDE, CLI and editor-plugin logins, normally has to sign out and re-authenticate each client whenever they change identity. Conversations stay attached to the old account, and expiring credits are easy to miss until they disappear. This app changes that step: pick an account card, and it writes the credentials for the selected client, optionally copying chosen sessions to the target account. The result is one account library shared across WorkBuddy and CodeBuddy surfaces, with credit balances and token usage visible in the same window.

What's different

The central mechanism is a shared account store. WorkBuddy, CodeBuddy IDE and the VS Code plugin all switch from the same list, while the CLI uses the same library with an independent default account. Session copying is additive: the copied conversation gets a new identifier and is attributed to the target account, while the source account's copy remains. Copied conversations are then linked, so a later "associated sessions" view can show each account's copy, sync incremental changes, and resolve divergence by choosing one version.

That linking model is more than a convenience feature. It turns multi-account use into a small version-control problem, and the branch view makes that trade-off explicit when two accounts have edited the same conversation. The bundled Agent Companion floating bar adds another layer: it listens to Codex, WorkBuddy, CodeBuddy and Codeg sessions through client hooks or webhooks and shows running, waiting-for-confirmation and finished states. The trade-off is integration depth: CodeBuddy CLI and JetBrains plugin sessions are not monitored by that bar, and several clients must be closed and reopened during a switch.

Who should try it

Good fit: a developer or power user who rotates between WorkBuddy and CodeBuddy accounts to spread credit usage, and who wants conversations to follow them and expiry dates surfaced. The automatic rotation for the CodeBuddy CLI default account is aimed squarely at that workflow. Poor fit: a single-account user, or anyone unwilling to grant the app write access to authentication files and install hooks for the floating bar, gets little from the added complexity.

A documented alternative matters for access: a global npm package runs a local web UI with the same modules but no floating bar, which suits Linux users or those who prefer a terminal-driven service over a packaged installer.

Requirements and limitations

Switching requires writing the clients' auth files. On macOS that means granting App Management or Full Disk Access and restarting the app for it to take effect, as described in the macOS permission notes. In webui mode the permission belongs to the terminal process, not the app. CodeBuddy IDE must be opened and logged in manually once before switching works there, and the JetBrains entry is disabled by default and must be enabled in settings.

Ongoing care is part of the deal. Switching the CodeBuddy CLI closes a running CLI session and does not reopen it; that session is interrupted. Other clients can be closed and reopened automatically during a switch. The floating bar depends on each client's hooks or webhooks, so its usefulness tracks those integrations rather than being a standalone monitor. Builds are distributed for macOS arm64/x86_64, Windows x64 and Linux x64 via Releases.

HotRepo's take

HotRepo began tracking this repository on 2026-10-24, when it was 70 days old. Its only recorded signal is a Rust monthly-board position of #18 with +712 stars on 2026-10-25; there is no comparable daily-board history, so persistence cannot be judged. Check the project instructions for whether your exact client combination is covered — particularly whether you use JetBrains or need CLI session continuity — before committing to this workflow.