Explore the structure

Follow the connections.

Find what depends on your code. See what your code depends on.

15groups

42connections

207dependencies

MODULE MAPAll arms

Inspect a module ↓

UpstreamDownstreamCycle return

15 groups · 42 connections · drag to panSCROLL to zoom · CLICK to trace · ESC to clear

Every module has a story.

Select a node to trace its connections, or find a module in the explorer.

Keep exploring

From the map to your terminal.

COMPUTED FROM CODE

The pillars1 arms · crowns & evidence

The arms the walk proposes. Each crown is the unit that orchestrates its arm.

  click · the pillars   2 layers · 2 nodes · 1 edges · 0 unconnected · [LR]

┌───────────────┐ ┌───────────────┐  
│ CORE (5→ ·→9) ├◀│ EDGE (9→ ·→5) │  
└───────────────┘ └───────────────┘

Arm	Crown	Units	Evidence
CORE	click.core	15	crown — fan-out at least half the leader's (75)

Compiled arms live at /site/.work/pallets/click/.graphy/GRAPH.md. Open one arm; blast its crown.

The package ring0 connected packages

Minted beside click: none.

Not carried: _typeshed, typing_extensions.

Add your modelMCP configuration

Paste this into the repo's .mcp.json (Claude Code) or your client's MCP settings. The client can start anywhere in the repo. Any model; the walk is graphy's.

{
  "mcpServers": {
    "graphy": {
      "command": "/usr/local/bin/graphy",
      "args": [
        "mcp",
        "--repo",
        "."
      ]
    }
  }
}

Ask the codebaseThree starting points

/usr/local/bin/graphy blast click.core --tenant /site/.work/pallets/click/.graphy/tenant.json --tenant-id clickif click.core changes, what breaks
/usr/local/bin/graphy descend click.core --tenant /site/.work/pallets/click/.graphy/tenant.json --tenant-id click --depth 3what click.core reaches, across packages
/usr/local/bin/graphy draw --tenant /site/.work/pallets/click/.graphy/tenant.json --tenant-id click --symbol click.core --radius 2 --lrthe neighbourhood, drawn

Make your own atlasOne command · no model

pip install graphyos
cd <repo> && graphy eat . && graphy showcase .

https://github.com/pallets/click.git
Every edge comes from code structure, a wormhole between packages, or a label resolved through the code's own scope. The module map shows cross-group connections with at least 2 dependencies; 20 below that floor.