Setup guide · macOS · v2.0.0

Install TORTUGA

Start to finish, about ten minutes. One computer holds the memory. Every other computer connects to it. There’s nothing to configure.

Install once

TORTUGA Server

Goes on the computer that stays on — a desktop, a spare machine, a home server. It holds the memory and shares it.

Install everywhere else

TORTUGA Client

Goes on every other computer. It finds the server and wires up Claude by itself.

Before you start — pick your server machine. The whole team’s memory lives there, so choose the one that’s on the most. If it sleeps, the others can’t reach the memory (nothing is lost — they just can’t read or write until it’s back). A laptop that travels is a poor choice. A desktop that never moves is perfect.
Part one

Set up the Server

Do this once, on your always-on Mac.

1

Run the installer

On the always-on Mac
  1. Unzip TORTUGA-Server-Mac.zip.
  2. Drag TORTUGA Server to your Applications folder (optional, but tidy).
  3. Right-click it and choose Open — not a double-click, the first time.
  4. macOS will say it’s from an unidentified developer. Click Open anyway.
Why the warning? TORTUGA isn’t code-signed with Apple yet. Right-click → Open is how macOS lets you run it regardless. You only do this once. Check the download against the checksum on your download page if you want to be certain.

A Terminal window opens and shows you what it’s doing. It takes a few seconds.

2

Enter your password when asked

On the always-on Mac

macOS shows a password box: “TORTUGA needs permission to share your memory folder with your other computers.” Enter your Mac password and click OK.

This is the only password TORTUGA ever asks for, and only on the server machine. It’s turning on file sharing for one folder — the same thing you’d do by hand in System Settings. If you cancel it, TORTUGA tells you and shows you how to do it manually.
3

Restart Claude

On the always-on Mac

Quit Claude completely with ⌘Q and open it again. Closing the window isn’t enough — Claude only reads its settings when it starts.

Check it worked

Ask Claude: “Read my shared-memory graph — how many entities?”
If it answers, the server is live. If you already had a memory graph, it’s all there — TORTUGA brought it across and kept a backup of the original.

Your dashboard is now at http://localhost:8787 — graph size, connected computers, and snapshots.

Part one and a half

Fill the brain

The step that makes it click. Do it before you add other computers.

★

Tell Claude to remember everything

On the always-on Mac

Your memory is empty right now. It works — but it doesn’t know anything yet. Fix that in one sentence. Ask Claude:

Remember everything you know about me and my work in the shared memory.
Go through our past conversations and write what matters — clients,
projects, decisions, how I like things done — into the knowledge graph.

Then let it run. It will read back through what it knows and write it into the graph as entities, relations and observations.

This takes a while — that’s normal. Depending on how much history you have, it can run for several minutes and make a lot of tool calls. Let it finish. You’re not waiting on TORTUGA; you’re waiting on Claude reading its own history. It only happens once.

Watch the entity count climb on your dashboard at http://localhost:8787 while it works. That’s your brain filling up.

Why this matters

Everything Claude writes now is what every other computer will know the moment it connects. Seed it first and your second machine arrives already knowing your clients, your projects, and how you work — instead of starting from zero and slowly learning it again.

Do this any time, not just at setup. Finished a big piece of work? Say “write what we figured out into the shared memory.” Every other agent on your network has it instantly.
Part two

Connect your other Macs

Repeat for each additional computer. About a minute each.

4

Run the client installer

On every other Mac
  1. Unzip TORTUGA-Client-Mac.zip.
  2. Right-click TORTUGA Client → Open, then Open again at the warning.

It finds the server on your network by itself — there’s no address to type. Then it connects the memory and wires up Claude.

It may ask you to log in to the server computer. That’s the username and password of the server Mac — the same as connecting to any shared folder. Tick “Remember this password” and you’ll never see it again.
5

Restart Claude

On every other Mac

Quit Claude fully (⌘Q) and reopen it.

You’re done

Ask Claude: “What do you know from my shared memory?”
It should answer with what the other computer knows. That’s the shared brain — in regular chat, in Cowork, and in Claude Code.

That’s the whole setup. Every agent on every computer now reads and writes the same memory. When one Claude learns something, the others already know it — no briefing, no repeating yourself.
If something’s off

Troubleshooting

The handful of things that actually go wrong, and the fix for each.

The client says it can’t find the server

Three usual causes, in order: the server Mac is asleep or off; the two computers are on different networks (guest Wi-Fi and VPNs both do this); or sharing didn’t get turned on during the server install.

On the server, open http://localhost:8787 — if that page doesn’t load, TORTUGA isn’t running there. You can also point the client straight at it from Terminal:

tortuga join --host 192.168.1.42

(Use your server’s address, shown on its dashboard.)

macOS says the app is damaged, or nothing happens

That’s the quarantine flag macOS puts on downloaded files. Right-click → Open rather than double-clicking. If it still refuses, open Terminal and run:

xattr -c "/Applications/TORTUGA Server.app"

Claude doesn’t see the memory after installing

Claude only reads its settings at launch. Quit it completely with ⌘Q — closing the window isn’t enough — then open it again.

It stopped working after a reboot or sleep

The connection to the server drops when a Mac sleeps or changes networks. TORTUGA reconnects on its own within a minute. If it doesn’t, run the client installer again — it’s safe to run as many times as you like.

I already had a memory file. Where did it go?

Nowhere. The server install copies it into the new home, keeps a dated backup beside it, and never touches your original. If TORTUGA can’t reach your old memory (say it lived on a drive that isn’t plugged in), it stops and tells you rather than starting you with an empty brain.

How do I remove it?

Run tortuga uninstall on the server, or tortuga leave on a client. Neither deletes your memory — the graph and every snapshot stay exactly where they are.

I’m on Windows

The Windows build is in final testing. Email sales@thetortugaai.com and we’ll send it the moment it’s ready, at no extra cost.

Still stuck? Email sales@thetortugaai.com or call (307) 288-3823. Tell us which step you’re on and what the window said — that’s usually enough to sort it in one reply.