Open source · Local-first CLI

Analyze once.
Reuse context everywhere.

devmap scans your project once, routes, dependencies, entry points, critical files, into a structured snapshot, so you stop re-explaining your codebase to every AI agent, every session.

View on GitHub →

MIT licensed. No account or API key required to start.

devmap analyze
lib/auth.ts
critical · referenced by 4 files
lib/db.ts
data access layer
app/api/session/route.ts
entry point
prisma/schema.prisma
schema source

One snapshot. Reused by every question after this.

Modern AI writes code faster than you can understand it.

01

You point your AI agent at an unfamiliar codebase.

02

It reads dozens of files trying to piece the architecture together, burning tokens and time.

03

It still gets it wrong, and starts over from zero next session.

devmap fixes this: analyze once, reuse the map every session after.

Three commands. Full understanding.

01 devmap init

Connect your AI provider. Done in 30 seconds.

02 devmap analyze

Scans your project with static analysis. Framework, routes, dependencies, entry points, critical files. No token waste, no guessing.

03 devmap explain "how does auth work?"

Get a targeted answer instantly. Reads the snapshot, not your entire codebase.

How it works

80%

One analyze pass builds the whole picture, structure, routes, dependencies, critical files, once.

20%

Wherever a model is involved, enrichment, narration, answers, it reads that snapshot instead of your raw code.

Your AI agent is only as good as its context.

Without DevMap, your AI agent explores your codebase blindly, opening files one by one, guessing what matters, rebuilding context from scratch every session.

With DevMap, your agent gets a ready-made project map. Framework, entry points, critical files, data flow, all structured, all accurate, all generated from static analysis.

devmap init DEVMAP.md
devmap analyze .devmap/snapshot.json

Your AI agent reads the map. Not the entire codebase. Faster execution. Lower token usage. Better results.

Compatible with: Claude Code, Codex, Gemini CLI, Cursor, Copilot

Ask your codebase. The right command answers.

  • devmap init
  • devmap analyze
  • devmap onboarding
  • devmap map authentication
  • devmap flow authentication
  • devmap explain "authentication feature"
  • devmap doctor
how do I get started
devmap init
Provider: ✓ Groq
API Key: ✓ Valid
Project: ✓ Next.js detected
Run: devmap analyze

How do I get started?

what is this codebase
devmap analyze
PROJECT devnote
FRAMEWORK Next.js
Entry Points → app/layout.tsx
Critical Files → lib/auth.ts

What is this codebase, structurally?

where do I start reading
devmap onboarding
Start here:
1. app/layout.tsx — root layout
2. lib/auth.ts — session handling
3. lib/db.ts — data access

Where should I start reading this project?

what does auth connect to
devmap map authentication
auth.ts
├─ used by → session/route.ts
├─ used by → middleware.ts
└─ uses → db.ts

This file/feature — what does it connect to, and how?

how does login work end to end
devmap flow authentication
1. POST /api/session
2. validateCredentials()
3. createSession()
4. redirect → /dashboard

How does this feature work from start to finish?

how does auth work
devmap explain "authentication feature"
Handles session creation and validation.
Imports db.ts for user lookup.
Imported by 4 files. Marked critical.

What does this file/feature/function do, in detail?

why isn't this working
devmap doctor
DevMap version 0.1.0 ✓
Provider Groq ✓
API key valid ✓
No issues found.

Why isn't this working?

New to a codebase? Know where to start in minutes.

devmap onboarding answers the one question every developer asks when joining an unfamiliar project:

"Where do I even begin?"

Prioritized reading list with estimated time per file

Recommended learning path optimized for understanding

Feature map, which files own which features

Modification guide, where to start when changing anything

Safe areas, caution areas, critical areas

Estimated time to productive contribution

DevMap vs. Going in blind

Without DevMap With DevMap
How structure is found Agent infers by reading code, live Static analysis (AST), computed once
What gets sent to AI Whatever the agent decides to read Curated index + feature map, not full source
Context per session Rebuilt from scratch Cached snapshot, reused
Starting a new session No starting point Ordered reading path, with reasons
Works across AI tools Re-explained per tool One snapshot, every agent

Free. Open Source. Forever.

DevMap is MIT licensed and free to use. No subscription. No account required. No DevMap servers involved.

If DevMap saves you time, consider supporting development.