Running two Claude Code accounts side by side with separate config folders
10/25/2026 — 10/25, 04:16·1 sources (all)·1 reports (all)
Key takeaways
- A tutorial explains that Claude Code keeps each account's login, settings, history and MCP servers in a single folder, so pointing different…
Background & analysis
On October 25, 2026, the AI section of DEV Community published a guide titled "Running two Claude Code accounts at the same time". The author discloses that they build Claude Sessions Pro, a paid Mac and Windows app for running several Claude accounts at once, notes that everything in the article works without it, and reserves a clearly marked section near the end for the app.
The article describes a common setup: a user has a work Claude account and a personal one, or one account per client. Claude Code signs in to a single account, so switching between them means running /logout and /login, dealing with a browser tab, and losing your place in the conversation. An hour later the reverse switch may be needed again.
The method presented relies on where Claude Code stores its state. Login, settings, history, and MCP servers all live in one folder per account, so pointing the CLI at a different folder at launch lets two terminals run two accounts side by side without repeated /logout and /login. The article walks through the steps on macOS, Linux, Windows (PowerShell, cmd, and Windows Terminal), plus VS Code and CI, and closes with a list of common mistakes that cause both terminals to silently share the same login.
No further developments have been reported since the article was published, so the technique rests on that single write-up and its instructions stand as given, unverified by any other coverage. A follow-up note suggests the approach extends to GPT, Gemini, and other similar coding assistants.
AI-generated from 1 reports · updated 12 hours ago
Related AI tools
- Heat index
- 70
- All sources
- 1
- All reports
- 1
- First seen
- 13 hours ago
Reports on this story headlines open the original
Claude Code keeps an account's login, settings, history and MCP servers in a single folder, so pointing it at different folders at launch lets two accounts run side by side in separate terminals instead of cycling through /logout and /login. The guide covers macOS, Linux, Windows (PowerShell, cmd and Windows Terminal) plus VS Code and CI, and lists the common traps that quietly put both terminals on the same login.
DEV Community · AIAI score 54
Other stories people are talking about
- Heat index 51Claude Code in Practice: How Non-Developers Build Projects with AI1 sources
- Heat index 96New10 Claude Code environment variables worth setting1 sources
- Heat index 60Developer compares v0 and Claude Code for UI work1 sources
- Heat index 49Codex and Claude Code writing tests in isolated worktrees1 sources
- Heat index 95NewClaude Code pricing: Pro from $20, Max from $1001 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

