I now run two copies of Claude Code. My company gave me a seat for company work, and I still pay for my own, which I use for this site, my business, and the small tools I build for myself.
The company seat exists so I can do company work faster. My own subscription existed long before it, and everything I built with it is mine. Both run the same tool with the same model, so it would be easy to open whichever one is closer and get on with the task.
I decided early not to do that. The company pays for its seat, sets its own rules for code and data, and trusts me to use it for the job. My personal projects deserve the same care in the other direction: my clients’ work and my own business shouldn’t sit on an account someone else administers.
How They Are Split
The split is physical. The company account is signed in on the company laptop, and my own account is signed in on my personal machine. Neither account is ever signed in on the other machine.
01
A new taskA ticket, a client request, or an idea of my own
02
Whose work is it?
CompanyCompany laptop, company account, company repositories and tickets
MinePersonal machine, my account, my site, business, and tools
Each side has its own instruction files, its own memory, and its own connected tools. The company side knows the company’s projects and conventions. My side knows my projects, my writing rules, and the shared vault my agents read from. Neither knows about the other.
The Line I Keep
Company seat, company tasks
Tickets, company repositories, internal documents, and anything a teammate might pick up after me. If the company would expect to own the result, it starts on the company laptop.
Personal seat, personal work
This website, my own business, freelance work for my own clients, and things I’m learning for myself.
Nothing crosses in files
No company code, data, credentials, or screenshots go into my personal setup, and I don’t open my own projects on the company account. Copying a file between machines “just for a quick look” is where a clean split usually starts to leak, so I don’t do it.
Ideas can cross
If I learn a better way to structure a prompt or review a change at work, I’m allowed to remember it. When I use that idea at home, I write it again from scratch for my own project.
Keeping It Light
This sounds strict on paper, but most days I don’t think about it. The machines do the separating: whatever is open in front of me already belongs to one side. I only stop when a task sits in between, like a tool that would help at work and at home. Then I ask myself who would own it, and I build it on that side.
The company gave me a capable tool and left how I use it to my judgment. Keeping company work on the company seat is how I respect that, and it means I can write notes like this one without wondering what I’m allowed to share.
What It Costs
I maintain two sets of settings, instructions, and memories, and a habit I set up on one machine has to be set up again on the other. The two agents can’t learn from each other, so I sometimes correct the same mistake twice. When a good idea starts at work, I have to rewrite it at home instead of copying it.
Rewriting a small idea takes minutes, and untangling company work from my own after the fact would take much longer.