How Claude Code fits together

One session, many ways to reach it. Your files and the AI live on your Mac — remote, cowork, and cloud are just different doors into (or around) that core.

The stack — bottom is your files, top is the cloud
☁️

Cloud — claude.ai/code

A fresh session in Anthropic's cloud. No access to your Mac's files. Use it when you don't have your laptop. Bring work down with claude --teleport.

runs in cloud
separate lane · teleport ↓ to go local
Access — how you reach your local session
🖥️ In person at your Mac

Type in VS Code. Full speed, everything at hand.

📱 Remote Control phone → Mac

Drive this same local session from your phone. Run /remote-control, scan the QR. Mac must stay awake.

🤝 Cowork + Dispatch delegate

Text a task from your phone → your Desktop runs it → result comes back. Pair once via QR.

🔔 Notifications optional

Get pinged when a long task finishes, from anywhere.

all of the above point at ↓
YOUR MAC · local execution
🤖

Claude Code — the session

The agent that reads, edits, runs commands, and deploys. Full access to local files, terminal, and connected tools (MCP).

the engine
🧩

VS Code — your workspace

The editor where you open projects and watch changes happen. Claude Code lives inside it.

editor
📁

~/Claude — your files

The single root everything is built on. One subfolder per project. The foundation the whole stack sits on.

on disk
Which door to use, when
ModeRuns whereLocal files?Reach for it when…
🖥️ Local (VS Code)Your Mac✅ FullYou're at your desk — the default, full-power way.
📱 Remote ControlYour Mac✅ FullYou're away but want to steer the actual work on your Mac.
🤝 Cowork + DispatchYour Desktop✅ FullYou want to hand off a task and get the result back — no live steering.
☁️ Cloud (web)Anthropic cloud❌ NoneYou don't have your Mac at all. Teleport later to continue locally.
Two roots — don't mix them up
Visible · your work

~/Claude

Everything you make. One subfolder per project; deploys push out from here. This is the stuff that matters day-to-day.

Hidden · Claude's brain

~/.claude

How Claude remembers and behaves across sessions — config, memory, transcripts, safety nets. You rarely open it, but it's always working.

~/Claude/            # your projects — auto-scanned into this map
├── claude-system-map/  # This infographic — auto-generated
├── Pipedrive/         # Pipedrive → SeaTable CRM (import-ready CSVs)
└── uy-license/        # NL→UY licence guide → Cloudflare Pages

~/.claude/           # the hidden brain (config & memory)
├── CLAUDE.md        # global conventions — loaded every session
├── settings.json    # config · permissions · hooks (effort: max)
├── sessions/        # session transcripts & state → resume + summarise
├── projects/        # per-project data, incl. memory (facts that persist)
├── file-history/    # change history  ┐
├── backups/         # file backups     ├ safety nets
├── shell-snapshots/ # your shell env   ┘
└── ide/             # the VS Code integration link

The ~/Claude rule and your settings live in ~/.claude — that's why every new session already knows how you work.

Active helper apps & services
🐙 GitHub ✓ installed

Version control & collaboration. Claude Code commits, pushes branches, and opens pull requests.

code + history
🟧 Cloudflare Pages ✓ installed

Instant static hosting via wrangler pages deploy — the licence guide & this page live here.

hosting · deploy
🟦 SeaTable

No-code database / spreadsheet. The free CRM replacing Pipedrive — CSVs import straight in.

database · CRM
🎈 Fly.io

Deploy full apps & servers close to users — for anything beyond a static site.

app hosting
🌐 Netlify

Alternative static / Jamstack hosting with deploy previews.

hosting
🔌 MCP connectors

Plug external tools & data (databases, APIs, drives) into a session so Claude Code can use them directly.

integrations
This map stays current

🔄 It rebuilds itself from live sources

Last generated 22 Jul 2026, 13:21 · 3 projects · 6 services