The work agent at work, your own agent at home

Many agents, one playbookDeveloper with an employer-approved agent and personal side projects

At work we use the agent the company approved. At home we use Claude Code on side projects. We wanted memory at home, and we did not want anything from work leaking into it, or the other way round.

How do I keep my AI agent's memory for side projects separate from my work projects?

Use a personal ArcRoom account and key on your home machine for side projects. Nothing from the work laptop reaches that room unless arcroom init was run there with that key, and arcroom whoami shows which key and team you're on. Using ArcRoom at work is your employer's call, and there is no SSO, SOC 2 or admin approval flow yet.

Also asked as: I don't want work code leaking into my personal AI agent's memory. How do I keep them apart? · How do I see what my agent memory tool has sent from this machine? · Can I use agent memory on side projects without touching my work setup?

The work

Home projects use a personal ArcRoom account and key on the home machine.

ArcRoom keeps
    The next agent gets

    $ arcroom whoami

    Step by step

    1. Home projects use a personal ArcRoom account and key on the home machine.
    2. Nothing from the work laptop reaches that room unless arcroom init was run there with that key, and it shouldn't be.
    3. Using ArcRoom at work is the employer's call: it sends prompt starts, paths and commands to ArcRoom's API.
    4. If the work agent is Copilot, Windsurf or Gemini CLI, ArcRoom doesn't support it anyway.

    What the agent sees

    $ arcroom whoami
    key: personal · team: home-projects
    $ arcroom sent --all
    (only side-project events from this machine)

    Compared with today's tools

    Vendor memory on each machine

    Let each agent's own memory work separately at work and at home.

    Setup
    none
    Ongoing
    none

    ArcRoom

    Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

    Setup
    2 min (npx arcroom init) at home
    Ongoing
    None

    At work, the approved vendor's memory is the honest answer today; at home ArcRoom adds memory that crosses agents.

    Where it stops

    No SSO, SOC 2 or admin approval flow, so many employers won't approve it yet. Two accounts on one machine is not a setup we document.

    Try it in your project

    Works with the agents your team already uses, and any agent over MCP or the HTTP API.

    More in many agents, one playbook