Multiple Claude Code accounts, one TermLink list
Your TermLink sign-in and your Claude Code sign-in are two different things. Register a personal machine and a work machine under one TermLink account, and see both in the same list — even though each is logged into Claude Code as someone different.
TermLink's account is the Google sign-in that lists your machines. Claude Code's account is whoever you ran claude login as, on that machine. They are not the same account, and TermLink never asks them to be — which turns out to be useful the moment you have more than one Claude Code seat.
Two sign-ins, not one
Registering a machine with TermLink and signing that machine's Claude Code into an account are separate steps, done with separate tools:
termlink login # this machine → your TermLink account
claude # sign in here, in this machine's own Claude Code
The host does not read, store, or forward Claude credentials — it checks that you are signed in to claude and then drives sessions through Claude Code's own SDK from there. Nothing about who you are to Claude Code and nothing about who you are to TermLink has to match.
Why that is useful
Because the two logins are independent, they can be different accounts without TermLink caring:
- Your personal laptop keeps your own Claude subscription. Your work laptop keeps your company's Claude Code seat. Register both machines under the same TermLink account and you get one list with a session from each — you switch between a personal account and a work account by switching cards, not by signing out and back in anywhere.
- A freelancer working under more than one client's Claude Code seat can do the same thing per project machine, without juggling
claude logoutbetween jobs. - Whichever account a machine's Claude Code is signed into, that is the account billed for that session's usage — TermLink does not change what a session costs or who it belongs to on Anthropic's side.
None of this needs a setting. It falls out of TermLink and Claude Code simply not sharing an identity system.
What this is not
It is not single sign-on, and it is not account switching inside a session. Each machine keeps whichever Claude Code account you signed it into until you change it there, the normal way (claude logout, then sign in again). TermLink's contribution is narrower and, for this, more useful: it puts sessions from accounts that have nothing to do with each other into one list, because the thing TermLink lists is machines, not identities.
It is also worth being direct about what TermLink's own account controls: who can see the list at all. Registering a machine under your TermLink account does not expose it to anyone else's — see what the relay can and cannot see for the rest of that picture.
Frequently asked questions
Can I use TermLink with more than one Claude Code account?
Yes. Claude Code's sign-in lives on each machine, independent of TermLink's. Sign a machine into whichever Claude Code account you want it to run as, register it with termlink login, and it shows up in your TermLink list next to machines signed into other accounts.
Does TermLink merge or share Claude Code credentials between machines?
No, and it cannot — it never sees them. The host checks that claude is signed in on that machine and then talks to Claude Code through its SDK from there. Nothing about that account is copied anywhere, including to other machines on the same TermLink account.
Do I need a separate TermLink account for each Claude Code account?
No. One TermLink account can list machines running under as many different Claude Code accounts as you have — that is the whole point. What you get in return is one screen instead of several.
Which Claude account gets billed for a session?
Whichever one that machine's Claude Code is signed into. TermLink relays the terminal; it is not a party to Claude Code's own billing or usage.
Can two people share the same TermLink account to reach different Claude accounts?
That is not what session sharing is for. A shared session gives a guest full control of that one terminal, not a separate corner of your list — see what the relay can and cannot see for how sharing actually works, and use separate TermLink accounts for separate people.
New to TermLink? Start with getting started with TermLink. For running several sessions well once you have them, see managing multiple Claude Code sessions.