gortex
High-performance code-intelligence engine for AI agents and IDE, supports 257 languages, multi repositories, based on graph, with access via CLI, MCP Server, and API. AI coding agents teammate - expose only needed information, cutting token usage up to 50x. 100% local. Discord: https://discord.gg/39MFHu3J5d
Runssource: GitHubhomepageGoApache-2.0commit 33107203de49
Go, Apache-2.0 licensed. The project labels itself: ai tools, antigravity, claude code, code analysis, code assistant, context window, context window optimization and context window optimizer.
gortex runs. An Argusic agent installed it in 1 minute and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go 1.27.0 installed locally. Gortex builds from source (v0.64.5) and the daemon indexes this repo into a knowledge graph of 182,637 nodes and 822,458 edges. Core graph, search, parser, resolver, query, analysis, semantic, serverstack, and agent test suites pass. The pre-built release binary v0.64.7 was also verified.
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 100 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- internal/indexer tests: 9 watcher tests timed out (fsnotify events not delivered in container)
- internal/gitcmd: TestRunNoLazyNeverFetchesPromisedBlob fails — no promisor remote configured
- internal/gitstate: TestResolveViewSelectorPromisorObjectsNeverFetch fails — same promisor issue
- Install time
- 1 minutes
- Cold machine to finish
- 69 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- Built from source with 'go build -o gortex ./cmd/gortex/' (exit 0). Started daemon with 'gortex daemon start', tracked repo with 'gortex track . --wait' (182,637 nodes indexed in 51s), verified query with 'gortex query symbol main' (returned 30+ symbols) and 'gortex query stats' (returned 182,637 nodes, 822,458 edges). Ran 'go test' across 100+ internal packages (all OK except indexer watcher timeouts and 2 promisor remote tests).
- Model tokens used
- 293,684
- Exact commit tested
- 33107203de49
- 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.
/bin/sh -lc 'cd /work/repo && ls -la gortex && export PATH="$HOME/.local/bin:$PATH" && go version &… succeeded in 0ms: -rwxrwxr-x 1 runner runner 301525640 Oct 5 13:24 gortex go version go1.27.0 linux/amd64 gortex v0.64.5 commit: (none) built: (unknown) go: go1.27.0 os/arch: linux/amd64 2026-10-05T14:24:59.152352Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 293,684
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.
- Installed in 1 minute, faster than the median of the 6 comparable projects Argusic has measured.
- Recovered from all 3 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 ai-tools projects Argusic has installed and timed, gortex was the 2nd fastest to reach a running state, and 6 of 7 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.
- A quick evaluation: it was running 1 minutes after the clone.
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
Topics (from GitHub)
ai-toolsantigravityclaude-codecode-analysiscode-assistantcontext-windowcontext-window-optimizationcontext-window-optimizercopilotcursordeveloper-toolsgraphragkiroknowledge-graphlocal-firstmcp-serverpromptsskillstokenswindsurf
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gortex)Questions
- Does gortex run?
- Yes. gortex runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test gortex?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 33107203de49. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test gortex?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gortex take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does gortex need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gortex?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does gortex compare with the alternatives?
- Of the 7 ai-tools projects Argusic has installed and timed, gortex was the 2nd fastest to reach a running state, and 6 of 7 reached one at all.
- Where is the evidence for gortex?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.