ig (Intent-Graph)
github.com/mrzdevcore/intent-graph- Category
- Developer Tools
- Rank
- No. 4028Tools index
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Coding · Software Testing & Quality
- Interfaces
- CLI · MCP
- GitHub
- 3 stars
- Latest release
- v0.1.2
- Date
About
A command line tool that reads a TypeScript, JavaScript, Python, Rust or Go repository and draws it as an interactive system map, from the whole system down to single functions. It can also show what a branch changes in the architecture and check committed architecture intent against the code, which helps reviewers follow AI-assisted changes across several projects.
At a glance
ig (intent-graph) is an Apache-2.0 command-line tool, a single Rust binary, that reads a TypeScript/JavaScript, Python, Rust or Go repository and draws it as a zoomable system map in one offline HTML page. You commit the architecture you intend as KDL files in ig/, and ig reports where the code has drifted from it. It can also draw a branch's architectural changes and answer questions on the map.
Good fit
Getting oriented in an unfamiliar repo in one of those four languages, reviewing what a branch does to module boundaries and dependencies, or enforcing an intended architecture in CI with ig check, which exits 1 on drift. Teams using Claude Code or another MCP client can let the agent read the map through ig mcp.
Consider something else when
Your codebase is mainly in a language other than TypeScript/JavaScript, Python, Rust or Go. Also skip it if you do not want to maintain a committed ig/ architecture file: the drift checks, ig plan and ig apply depend on keeping that file current.
Start here
Install with brew install mrzdevcore/tap/ig, then in the repo run ig init, ig analyse and ig view. Note that ig init adds ig.yaml, agent skills and an AGENTS.md snippet. Review the generated ig/ with git diff ig/ before committing it, then try ig diff main on a branch to see changed boxes and new arrows.
Cost and requirements
Free and open source under Apache-2.0. Homebrew installs it on macOS and Linux; a source build needs Rust, node and pnpm. Running it needs only git on PATH. The optional AI pass, which names and describes boxes, needs the claude, gemini or codex CLI, so any model usage is billed through that agent's own account.
Limits to know
The workspace version is 0.1.2, so expect an early project. The base map comes from parsing alone (packages, folders, imports, calls, file counts); box names, descriptions and pattern labels such as layered or hexagonal come from the optional agent pass, which hands your code to the agent CLI you choose. The command table says ig explore and ig apply use Claude specifically, and ig apply lets the agent write code after asking.
Still unclear
- Do ig explore and ig apply work with the Gemini or Codex CLI, or only with Claude?
- Is Windows supported? The documented installs cover Homebrew on macOS and Linux, or a source build.
- How well does the map hold up on large monorepos?
Sources checked 2026-11-21. Source-based assessment.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.