GRAPH walk before you read

engine · the gallery

GRAPH — arms for codebases the walk already cut

10 codebase(s), each drawn by one command: the modules, the pillars the walk proposes, the dependency ring, and the MCP block. No model decided an edge. Every page is a query over the code's own structure.

Law walk before you read Eat then harness Site graphy-os.com

The compile

After eat, graphy harness is the missing step: partition, arms, drawings, first walk, GRAPH.md. Curated bytes win.

  1. Pillarspropose only if partition.json is absent
  2. Arms generateinventory · inherits-out · re-walk — operator prose left alone
  3. Drawingspillars.svg + each ARM.svg, check_artifact
  4. First walkblast the crown, write .walk.txt
  5. GRAPH.mdthe hub: facts, real crowns, real paths
  6. Pointersthin CLAUDE.md / AGENTS.md only if missing or already a stub

The gallery

Ten repos people know. Open one page. Do not dump the tree into context.

uvx --from 'graphyos[typescript]' graphy showcase .        # your own repo, one page, no venv
pip install 'graphyos[typescript]' && graphy showcase https://github.com/you/your-repo.git
pip install graphyos && graphy eat . && graphy harness --repo .   # the hub: GRAPH.md

Or open an issue on omnislash157/graphyos naming a GitHub url — the CI posts your repo's page back, running nothing of your code.

Add your model

Paste into .mcp.json (Claude Code) or your client's MCP settings after graphy eat . — the tools: hunt · descend · blast · walk · draw · explain · history.

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