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

Описание и применение

Автор использует Claude Code на нескольких устройствах, но логины истекают на неактивных машинах, требуя повторного входа. С помощью ccdeck он добавляет несколько аккаунтов, экспортирует их и импортирует на другие устройства, а затем включает синхронизацию по локальной сети, чтобы автоматически обновлять истекшие токены.

Задача

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

Результат

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.

Рабочий процесс

• 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.

Доказательства

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.

Источник

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.

Источник

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

Источник

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

Источник

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.

Источник