INDAGO Code

New codebase? Thousands of warnings? An AI that guesses?

Every repo, understood.

INDAGO Code reads your repositories on your Mac, answers questions about them with file and line, and finds the issues worth fixing.

Get INDAGO CodeFree for 3 repos · macOS on Apple silicon

What it solves

From frustration to answer.

Weeks before a new hire is productive

A codebase brief and answers with file and line

Engineering teams

Scanners that drown real issues in noise

Findings ranked by reachability, with SARIF out

Security teams

“Where on earth is this handled?”

Ask in plain language; walk the call graph

Developers

Coding agents that invent functions

Your agent searches the real code before it writes

AI coding agents

How it works

Three steps to your first answer.

Add a repository

Local folders. No upload, no CI changes.

Run a scan

Security, quality and performance checks across 16 languages.

Ask about it

Where is this handled? Who calls this? Your AI can ask too.

Findings worth fixing.

67 security checks, dead code, complexity and performance — ranked, with the line that matters.

Security checks with call-path context
Dead code in 9 languages
SARIF export for your pipeline

The map of your code.

Follow any function through its callers and callees. Onboarding in an afternoon.

Call graph you can walk
Ask in plain language
Answers cite file and line

Your AI, grounded.

Connect Claude, Codex, Cursor or a local model. They search your code and cite what they find.

One-command setup
Works with local models
Less guessing, more citing

Your coding agent. Grounded in your code.

Claude Code, Codex, Cursor or a local model call INDAGO before they write — and cite file and line.

claude — ~/src/godot

> How does Godot dispatch input events to nodes?

⏺ indago · indago_find(query: "how are input events dispatched to nodes in the scene tree", mode: "code")

⎿ 6 results · ranked, with file and line

1. scene/main/scene_tree.cpp:1430-1443 SceneTree::_call_input_pause

2. scene/main/viewport.cpp:3642-3653 Viewport → _call_input_pause(unhandled_input)

3. scene/main/node.h:408-412 Node::_call_input · _call_shortcut_input · _call_unhandled_input

4. scene/main/viewport.cpp:3636-3640 Viewport → _call_input_pause(unhandled_key_input)

5. scene/main/viewport.cpp:3597-3624 Viewport → _call_input_pause(shortcut_input)

⏺ Input flows Viewport → SceneTree::_call_input_pause → Node::_call_input, in that order: input, shortcut, unhandled key, unhandled.

Real tool output · INDAGO on the open-source Godot engine; the agent's question and summary are shown for context.indago-mcp · INDAGO Code 0.7.9

Connect in one line.

Or one click: Settings → Integrations.

Terminal

claude mcp add indago -- "/Applications/INDAGO Code.app/Contents/MacOS/indago-mcp"

indago_find

Find

Ranked search over code, docs and past AI conversations.

indago_read

Read

Open the exact passage behind a result.

indago_code_graph

Call graph

Who calls this, and what does it call.

indago_findings

Findings

Security, quality and performance issues, ranked.

indago_brief

Brief

The shape of a codebase in one page.

indago_scan

Scan

Run checks on demand, export SARIF.

Made for you

Pick your world.

Your problem, your documents, your first five steps.

Developers

Understand any repo in an afternoon.

Security

Used across industries.

Research & universities

Used in 1 role

Legal, IP & compliance

Used in 2 roles

Dual use & security

Used in 3 roles

Business & industry

Used in 1 role

Developers & AI

Used in 3 roles

6,304/spassages indexed per second, CPU only

1.57 Mpassages in one index, on one workstation

<10mstypical search on real workspaces (p50 5–9 ms, Oct 2026)

2 minto read 65,839 Wikipedia articles on a Mac with M5 Max

Measured: production measurement windows, Oct 2026 (search) · INDAGO test report v1.1, Apple M5 Max, no GPU (indexing) · website demo. How we measured →

Find it in a blink.

Your documents stay on your Mac.

Get INDAGO Code See the benchmarks

macOS · Apple silicon · Signed and notarised