Two Claudes, One Machine

1 · the problem

The work account felt like half a Claude

The Team seat lives in a browser: no terminal, no files, no plugins, no local tools. And switching one app between two logins means losing memory, connectors and walls every time you swap.

"If I can't use Claude Code at work, what's the point of having a work account?" — fair question. Here's the answer.

2 · the idea

Profiles: two fully signed-in Claudes, picked by name

Claude Code can run from any config folder. Give each account its own folder and each stays permanently signed in — with its own memory, plugins and settings, fully walled from the other.

You type	You get	It knows about
`claude`	Personal Claude — your own account, as always	Everything yours
`hi-claude`	Work Claude — the hi! Team account, full engine	hi! only, by construction

They can run at the same time, in two terminal windows. Work Claude burns Team-plan usage, not your personal plan.

3 · Elizabeth's machine

Built. One sign-in left.

✓ Work profile created, walled off from personal
✓ hi-fleet plugin pre-installed (all agents + skills)
✓ Clock hook wired (Claude always knows the real date)
✓ hi!-only orientation file in place

The one act

Open Terminal, run hi-claude, sign in once with amoelizabeth@thehiagency.com. Done forever.

4 · Stacy's machine

Same setup, one paste

Paste this into your personal Claude Code and it builds your work profile for you:

Set up a second Claude Code profile for my hi! work account, using
the CLAUDE_CONFIG_DIR pattern:

1. Create the folder ~/.claude-hi
2. With CLAUDE_CONFIG_DIR=~/.claude-hi, run:
   claude plugin marketplace add https://github.com/the-hi-agency/hi-agents.git
   claude plugin install hi-fleet@hi
3. Add the clock hook: in ~/.claude-hi/settings.json, register a
   UserPromptSubmit hook running
   "python3 ~/.claude-hi/plugins/marketplaces/hi/scripts/inject_time.py"
4. Add to my shell profile:
   alias hi-claude='CLAUDE_CONFIG_DIR=$HOME/.claude-hi claude'
5. Write ~/.claude-hi/CLAUDE.md saying: this profile is for hi! work
   only, signed in as stacy@thehiagency.com; the hi! tree and its
   CLAUDE.md govern; personal matters stay on my personal profile.
Then tell me to run hi-claude and sign in with my work email — that
sign-in is my step, do everything else yourself.

After the one sign-in: claude = your personal, hi-claude = work. Aimee rides along in both — she's in the fleet plugin.

5 · memory

Give the work account a brain — carefully

The browser seat has a memory import: Customize → Memory → Start import. It hands you a prompt to run in your other account, then you paste the results back.

The one rule: curate, never dump

Your personal Claude's memory holds your whole life. The work account lives in an org workspace. Never paste a raw export — have your assistant write a work-only version first (founders, business facts, working styles, nothing personal). Elizabeth's went in today, curated: 40 lines of hi! context, zero personal content.

Also on that page: leave "Include sensitive topics" off for work seats.

6 · which Claude, when

Engine room vs. shared table

Use	For
Personal Claude (app / `claude`)	Your own projects, your automations, your memory, your walls
Work Claude (`hi-claude`)	Building for hi! — code, docs, client work, on the Team plan's usage
Work seat in browser (claude.ai)	What we share: joint Projects, Cowork, presenting together, org skills

Rule of thumb: anything the other founder should see starts on a shared surface. Engines produce; the table is where it lands.

7 · where it stands today

Live as of Sunday afternoon

✓ GitHub org the-hi-agency — 4 repos, both founders owners
✓ Elizabeth's Team seat: joined, instructed, memory imported (curated)
✓ Work-seat connectors: Asana · GitHub · Drive · Calendar · Slack
✓ All 16 fleet skills uploaded to the work seat
✓ Fleet v0.7.0 everywhere — Cairo, both assistants, the new standards
Waiting: Stacy's M365 connector approval (unlocks SharePoint) · Stacy's hi-claude paste · both founders' one sign-in each

Questions land in Slack — Daisy and Aimee both know this whole setup.