ArchDraw

Live maps for Claude Code · free, no account

Six agents are coding. Which one needs you?

A live map of your codebase with every Claude Code session on it.

No credit card required.
Only file names and paths leave your machine.
Or draw a diagram in the browser →

  • working
  • heading there
  • needs permission
  • finished, your turn
  • new code, not on the map yet

The problem

Parallel agents.
Serial attention.

You started six sessions to go faster. Then you spent the afternoon cycling through tabs, looking for the one that has been waiting eleven minutes for a yes.

Your terminal tabsclaude × 6

Every session gets a name, a star on the map and a terminal title that tells you when it’s blocked.

How it works

Three minutes to a live map.

  1. 01

    Run one command in your repo

    It reads folder names and imports on your machine, sends only names and paths, connects Claude Code and opens your live map. No account, no config file.

  2. 02

    Let Claude draw the real map

    Say yes and your own Claude Code reads the repository, read-only. The overview lands in one to three minutes; the detailed map follows.

  3. 03

    Start your sessions

    Each new Claude Code session in the repo appears as a named star and walks to the code it is working on. Run as many as you like.

~/code/acme-shop $ npx archdraw-live
Setting up a live map for acme-shop…
✓ Mapped 9 components and 3 services from 412 files (on this machine)
✓ Project created (link saved in ~/.archdraw/projects.json, outside your repo)
✓ Claude Code connected (hooks in ~/.claude/settings.json)
Let Claude read your code and draw an accurate map? [Y/n] y
Claude is reading your code (read-only) to draw the map.
✓ Claude mapped 14 components (the live map has updated)
✓ Detailed map: 46 parts (switch to "Detailed" at the top of the live map)
Next: start Claude Code in this folder (run claude).

On the map

Everything a glance
should tell you.

Who needs you, in order

Permission requests first, longest wait first. The terminal tab says it too, and browser notifications are one click away.

New code shows up before the map does

When an agent writes code no component owns, a dashed site appears next to the closest one. Update the map and it becomes a real box.

Overview, then the detail

A one-screen overview of how the system works. Switch to Detailed to open every component into its modules and files.

See where a task is headed

Send a prompt and the session’s star points at the part of the system it’s about. The prompt is matched on your machine and never sent.

Share it live

Send a read-only live map to a teammate or a client. They watch without signing in.

Know when the map drifts

Edits outside the map lower its coverage, so you know when it’s time to ask Claude to re-map.

What leaves your machine

Paths, never code.

Sent to ArchDraw

  • Component names and the folders they own
  • Which files each session reads or edits
  • Session status: working, waiting, done

Stays on your machine

  • File contents and diffs
  • Your prompts, matched to the map locally
  • Your agent token, kept in ~/.archdraw, outside the repo and out of Claude’s context

Don’t take our word for it.

$ npx archdraw-live --dry-run

prints exactly what would be sent, and sends nothing.

$ npx archdraw-live stop

disconnects the repo.

Made for

However you build with agents.

i.

You run agents in parallel

Five sessions, three worktrees, one screen. See all of them at once and answer the one that’s blocked first.

ii.

You build by prompting

You don’t read every diff. The map shows what is being built and where, in boxes and arrows you can follow.

iii.

You’re new to a codebase

A real architecture map in minutes, drawn from the code, with every box tied to the files it owns.

Questions

Good to know.

Need a diagram rather than a live map? Describe a system, map a public repo or draw from your agent.

Is it free? Do I need an account?

It is free, and you don’t need an account to start. Sign in with Google or GitHub to keep a project and edit its diagram; you can keep two. Projects nobody saves are deleted after 30 days without activity.

Does it work on private repositories?

Yes. The scan and the mapping run on your machine, so the code never has to be public. ArchDraw only receives component names, folder paths and which files each session touches.

Which coding agents does it follow?

Claude Code, through its hooks. Every session started in a connected repository appears on the map, including sessions in git worktrees of that repository.

Does mapping use my Claude plan?

Yes. The map is drawn by your own Claude Code with read-only tools (Read, Grep, Glob). The overview takes one to three minutes, the detailed map a little longer. You can skip it and keep the folder-based map.

Will it slow my agents down?

No. Each report is a few file paths sent from a background process, so a slow network never blocks a session.

How do I disconnect a repository?

Run npx archdraw-live stop in it. Sessions there stop reporting right away.

Open the map.
Then start the agents.

Free. No account to start. Needs Node 18 or later and Claude Code.