Claude Code transcripts. Cursor chat history. Devin's Cascade memories. Copilot sessions. Agent skills, memory, and MCP configs sit in folders iCloud never syncs — on Macs where Time Machine is usually off entirely and iCloud never syncs. Loadout encrypts them on your Mac and backs them up every 15 minutes — to storage that cannot read them.
curl -fsSL https://loadout.works/scan | python3
No install, no account, no network calls — the scanner reads file sizes and your backup settings, then writes an HTML report to the folder you're in. Piping to an interpreter deserves scrutiny, so read the source first — it's one file, and that's the whole point of us.
Two commands, then it's all buttons. Every line that runs on your machine is readable before you run it.
curl -fsSL https://loadout.works/install | bash
A short bash script that puts a single-file Python CLI in ~/.loadout/bin.
macOS, Python 3.9+. Read the installer and the CLI it downloads first if you like.
loadout
The installer builds Loadout.app into your Applications folder —
compiled on your own Mac, which is why there's no Gatekeeper warning. Native window, Dock icon,
About and Check for Updates in the menu bar where they belong. Everything runs against
127.0.0.1 on your machine. (Terminal fans: loadout does the same in a browser.)
Everything else is buttons in the dashboard:
Start free (30 days, no card) · Back up now (you choose a
passphrase — your key is derived from it on your Mac and never leaves it) ·
automatic backups every 15 minutes — a stat-level fingerprint check first, so an unchanged Mac costs zero upload and near-zero CPU ·
Restore · Sync skills to your other Macs · Move a conversation from Cursor into Claude Code.
Prefer the terminal? Every button has a command twin — loadout --help.
The data your AI tools quietly accumulate, and how badly it would hurt to lose it.
| Source | What's in it | Risk |
|---|---|---|
| Claude Code | Session transcripts, skills, agents, memory, MCP config | High |
| Cursor | Full chat & composer history, MCP config | High |
| Devin (was Windsurf) | Cascade state & memories, local agent state | High |
| Antigravity | Agent conversations, settings, workspace state | High |
| VS Code / Copilot | Chat sessions, user settings | Medium |
| Codex CLI | Sessions & config | Medium |
| Continue | Sessions & config | Medium |
| Aider | Chat history | Medium |
| Claude Desktop · LM Studio | App settings, local model configs | Medium |
High = irreplaceable history and agent memory. Medium = sessions and configs you'd rather not rebuild. MCP configs often contain live credentials, which is its own reason to keep them off unencrypted backups.
Model weights (Ollama, Hugging Face, MLX) are excluded on purpose: they're re-downloadable, and you shouldn't pay us to store them.
Loadout.app is a real Mac app with four screens — Backup,
Conversations, Skills, Settings — served from your own
machine at 127.0.0.1. See every source it protects and when it last snapshotted, switch sources
on or off, and see your skills across agents: every skill you've built, and which platforms each one is
active on.
claude-codecursor-globalwindsurf-devinvscode-usercodex-cliAn illustration of the dashboard, drawn in CSS — not a doctored screenshot. The real one is
loadout dashboard: it binds to 127.0.0.1 only and works offline.
Months of working context live inside each tool’s private storage. Loadout reads it — read-only, on your machine — and lets you take it with you.
The Conversations screen shows each AI tool on your Mac with a count of what it holds.
Pick a conversation and: Save as Markdown — a clean transcript on disk, yours forever —
or Send to Claude Code, which adds it to Claude Code as one of its own sessions: it shows
up in the app sidebar and in claude --resume, and you keep going where you left off.
Nothing is copied until you choose, nothing is overwritten, and every import is one file you can delete.
Honest scope: browsing works for Cursor and Claude Code today; Devin and Antigravity are backed up in full but not browsable yet. Destinations only appear for tools actually installed on your Mac. Switching tools? This is how you take your history with you.
The version we'd want to read, not the version that sells best.
| What we store | What we can never see |
|---|---|
Source names — claude-code, cursor-global… | The contents of any file |
| Encrypted blob sizes | Your passphrase or encryption keys |
| Snapshot timestamps and device name | Filenames inside your sources |
| Your email address | Your chats, prompts, or code |
The honest part: if you lose your passphrase, we cannot recover your data. Not "it would be difficult" — we hold nothing that can. That's not a limitation we're working on; it's the design. Put the passphrase in your password manager.
$9/month, or $79/year (about 3 months free) — and payments are not even wired up yet. When your month ends, we will ask, not charge.
One tier. Everything included. If the trial ends and you walk away, your existing snapshots stay restorable.
Yes — and you should. Every line that runs on your machine is visible: the scanner at loadout.works/scan and the full CLI at loadout.works/cli, both single Python files. Loadout is source-visible, not open source: you can audit everything we ship to you, and the license reserves the rest. We think you deserve to verify our security claims; that doesn't require giving the code away.
Because it gets you a less scary app, not a more scary one. The installer compiles Loadout.app on your own Mac — locally built software carries no Gatekeeper quarantine, so there's no "unidentified developer" warning to click through, and nothing runs before you've had the chance to read exactly what the installer does. A notarized downloadable .app is coming; the local build is how we ship a first-class app experience without asking you to bypass macOS security in the meantime.
macOS first. The data paths, the launchd schedule, and the Keychain integration are all macOS-specific today, and we'd rather do one platform properly than three badly. If you want Windows or Linux, tell us: hello@loadout.works — it genuinely affects the order we build things.
Your existing snapshots become unreadable — to everyone, including us. There is no reset flow because a reset flow would mean we could read your data. Store the passphrase in a password manager; future backups can start fresh with a new one.
No. Everything is encrypted on your Mac before upload, and the key never leaves it. What we can see is metadata: source names, encrypted sizes, timestamps, device name, your email — and, because dedup is deterministic, whether a source changed between snapshots. That's the complete list.
Because you can read it. The whole client is one Python file — no compiled binary you have to take on
faith. For a product whose pitch is "trust us with your data," that matters more than a fancier stack.
It needs Python 3.9+ and the cryptography package, which the installer sets up.
We email and ask. Payments aren't wired up yet, so nothing can auto-charge — there's no card on file to charge. If you don't subscribe, new backups pause but your existing snapshots stay restorable.