how do I get started
devmap init Provider: ✓ OpenRouter
API Key: ✓ Valid
Project: ✓ Next.js detected
Run: devmap analyze
How do I get started?
Analyze once.
Reuse context everywhere.
DevMap analyzes your codebase once and builds a reusable context layer. Routes, dependencies, entry points, critical files — all structured so you stop re-explaining your project to every AI agent, every session.
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.
How it works
Static analysis
One analyze pass builds the whole picture.
Structure, routes, dependencies, critical files — computed once
from your source code, deterministically.
Optional AI
Where a model is involved — enrichment, narration, answers — it reads the structured snapshot instead of your raw code. AI is an enhancement layer, not the foundation.
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
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 <current> ✓
Provider Groq ✓
API key valid ✓
No issues found.
Why isn't this working?
New to a codebase? Know where to start.
devmap onboarding answers the one question every developer asks when joining an unfamiliar project:
"Where do I even begin?"
Recommended reading path with entry points and critical files
Feature map — which files own which features
Key flows and how features connect end to end
Available commands to go deeper after onboarding
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.