Credentials. Janus stores saved OAuth tokens in the login keychain and moves the live session between accounts, so only use it on a Mac you control.
Who it is forA developer with a personal and a work Claude Code account who is tired of signing out and typing logins again.
The problemSigning in as another Claude Code account normally means signing out first and entering the whole login again.
The outcomeEach account is saved in Janus, and the live session can be switched with one click or the ⌘S shortcut from the menu bar.
What you need first
- A Mac running macOS (the README says macOS only)
- Claude Code or Codex installed and signed in to at least one account
- Homebrew, or a manual download of the latest .dmg from Releases
- Xcode Command Line Tools if you build from source
Steps
- Install Janus with
brew install --cask --no-quarantine ramitvishwakarma/tap/janus, or download the latest .dmg from Releases and drag Janus to Applications. - If you downloaded the .dmg by hand, run
xattr -dr com.apple.quarantine /Applications/Janus.apponce, then runopen /Applications/Janus.app. - With the first account signed in to Claude Code, open Janus and press Save current account.
- Sign out of Claude Code, sign in as the second account, return to Janus, and press Save current account again.
- Switch between the two accounts with one click or ⌘S from the menu bar, then restart Claude Code to pick up the new account.
Prompt for your agent
Using the Janus repo at RamitVishwakarma/Janus, explain how to save the Claude Code account currently signed in on this Mac and switch to <target account name>. Report the list of saved accounts and which one is live. Verify that the live account in the menu bar matches the account you switched to.
Caveat. Switching does not affect a Claude Code session that is already running, so you must restart Claude Code to use the new account.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page