Ix

Understand any codebase instantly. System intelligence for codebases, built for humans and AI.

Runssource: GitHubhomepageTypeScriptApache-2.0commit f36c4e0fc96a

TypeScript, Apache-2.0 licensed. The project labels itself: ai, ai memory, claude code, cli, code analysis, code mapping, code memory and codebase understanding.

Ix runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project builds from source, all 2561 tests pass (172 test files), the tree-sitter parser correctly extracts entities and relationships from source code, and the CLI binary responds to help and version queries.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.5 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
97.5 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
2
last tested
stars
1,159
forks
99
open issues
79
watchers
4
size
19 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing Ix, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 installed but project requires >=22.0.01 minute
  • Docker not installed in container (required for backend services)
Install time
12 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm run test:unit from ix-cli/ exited 0: 134 files, 2170 passed, 2 skipped. npm test from core-ingestion/ exited 0: 38 files, 391 passed, 1 skipped. node test/parser.smoke.mjs printed 'parser smoke test passed'. node dist/cli/main.js --version printed '0.10.5'. node dist/cli/main.js --help showed all commands.
Model tokens used
96,003
Exact commit tested
f36c4e0fc96a
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**CLI Verification** – `ix --version` prints `0.10.5`, `ix --help` prints all commands. `ix status`…
**Parser Verification** – `parseFile()` on a Python fixture returned 10 entities and 16 relationshi…
tokens used
96,003
Here's the summary:
**Install** – Built `core-ingestion` and `ix-cli` successfully. Only issue was Node.js v18 (project…
**Tests** – All suites pass:
- `ix-cli`: 134 test files, 2170 passed, 2 skipped
- `core-ingestion`: 38 test files, 391 passed, 1 skipped
- Parser smoke test: passed
**CLI Verification** – `ix --version` prints `0.10.5`, `ix --help` prints all commands. `ix status`…
**Parser Verification** – `parseFile()` on a Python fixture returned 10 entities and 16 relationshi…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 12 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.

Of the 237 ai projects Argusic has installed and timed, Ix was the 180th fastest to reach a running state, and 168 of 237 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs95.000.12
Argusic Runner1/3Runs100.000.05

Topics (from GitHub)

aiai-memoryclaude-codeclicode-analysiscode-mappingcode-memorycodebase-understandingcodexdeveloper-toolsllmopenclawpersistent-memoryprogram-analysissoftware-architecturesystem-intelligencesystem-mapping

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Ix.svg)](https://argusic.com/subject/ix)

Questions

Does Ix run?
Yes. Ix runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test Ix?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f36c4e0fc96a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Ix?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Ix take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does Ix need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Ix?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does Ix compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, Ix was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for Ix?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion