Two Claude Accounts, Revisited
A while back I wrote about using two Claude accounts side by side. A private subscription and a corporate team account, two config dirs and a pair of shell aliases so the tokens don’t bleed into each other. That part still works fine. But after living with it for a few months, I learned where it falls short, so here is the grown-up version.
Two setups drift apart
The aliases only solved which account pays.
They did nothing about how Claude behaves.
Each config dir grew its own CLAUDE.md, and the moment you maintain two of anything by hand, they drift.
I’d tighten a commit convention in one account and forget the other.
The work account learned a guardrail the private one never got.
What I really wanted was the same baseline everywhere, conventional commits, SHA-pinned GitHub Actions, license headers, no matter which hat I’m wearing.
