Stop running `claude login` on every machine — share your Claude Code accounts between your devices

Description and use

The author uses Claude Code on multiple machines, but logins expire on idle devices, forcing repeated logins. Using ccdeck, he adds multiple accounts, exports them, imports them on other machines, and enables local‑network sync to automatically refresh expired tokens.

Problem

Claude Code logins expire on machines that are not used, forcing a weekly claude login on the idle machine.

Outcome

After setting up ccdeck and enabling local network sync, the author no longer needs to run claude login on idle machines; expired logins are refreshed automatically.

Workflow

• 1. Add multiple Claude accounts to one machine using ccdeck’s accounts panel.
• 2. Export the accounts from that machine and paste the share text into another machine to import the logins.
• 3. Enable the Local network sync in ccdeck so that expired logins are automatically copied from a machine that still has a valid copy.
• 4. Configure which accounts each machine may share and pair the decks on the same network.

Evidence

That setup has one boring, recurring problem: a Claude login expires on the machine that has not used it for a while, and stays alive on the one that has.

Source

With two or three machines that is a claude login about once a week, and it always happens on the machine I am not sitting at.

Source

The share carries logins only: no projects, sessions, MCP servers or deck settings.

Source

The share is not encrypted. It is claude-swap's export, compressed and base64-encoded.

Source

With it on, decks on the same network find each other, pair, and a login that has expired on one machine is copied from another machine that still has a working copy, about once a minute.

Source