mrkeyoor.comAsk

zzet/gortextested 08 Oct 2026commit e129655

gortex review

Gortex is worth a controlled trial when your agents need relationships across repositories.

  • Install 206 s
  • Build 445 s
206/214passed, run exited non-zero
  • 417 packages
Dev Toolsevaluationupdated 24 Oct 2026
+11stars / 7d

Gortex is a code-intelligence engine for coding agents and developers. Its README describes a persistent SQLite graph of symbols, calls and cross-repository contracts, queried through a CLI, MCP server, HTTP API and web interface. Our recorded source build succeeded; graph accuracy and agent efficiency were not measured.

Verdict

Gortex is worth a controlled trial when your agents need relationships across repositories. Our October 8, 2026 run at e129655 built successfully, but its test command exited with code 1; the supplied evidence does not establish the cause or prove the product is broken. Search-truncation issue 672 is now closed, while workspace-scoping issue 673 remains open in the supplied extracts. Validate known queries and workspace transitions before relying on graph answers. This review establishes source-build feasibility in one sandbox, not production readiness or measured token savings.

We ran it

Lab card: what happened when we ran gortex
Lab card from our sandbox run
Screenshot of gortex (gortex.dev)
gortex.dev
Install✓ · 206s417 packages
Build✓ · 445s
Tests✗ · 852s206 passed · 8 failed of 214 (go test)
Repo4930 files~1,176,896 lines of source · 48.9 MB · 10 CI workflows

Answers from our run

Does gortex build from source?

Dependencies installed in 206 seconds (417 packages), and the build succeeded in 445 seconds. We cloned commit e129655 into a clean Debian container with 3 CPUs and no project-specific setup.

Do gortex's tests pass?

No. The project's own test command finished in 852 seconds and reported 206 passed, 8 failed (go test).

Who should not use gortex?

Teams seeking independently verified indexing accuracy, query latency or token savings from this review: our run measured none of those workloads.

What are the alternatives to gortex?

Zoekt, Aider. Gortex is worth a controlled trial when your agents need relationships across repositories.

Setup3/5Controlled-trial support: the October 8 run at e129655 completed dependency setup in 206 seconds and built in 445 seconds. Installed-binary and agent-integration checks were not recorded.
Docs3/5The supplied installation guide explains binary platforms, source requirements and custom-grammar limits. README integration counts differ, and linked documentation was not comprehensively reviewed.
Community2/5Supplied issues contain detailed user reports, follow-up evidence and maintainer responses. Adoption and support responsiveness were not measured; star counts are not quality evidence.
Maturity2/5The supplied history records closure of search and PDF reports, but workspace issue 673 remains open. The October 8 test command exited with code 1, with unresolved causes in the available evidence.

Discussed on

  1. hnShow HN: Gortex – MCP server for cross-repo code intelligence3 points

Who it’s for

Developers evaluating graph queries for code spread across repositories.
Agent users who want symbol, call-chain and contract context through MCP.
Teams able to check graph results against known source queries before depending on them.
Operators prepared to supervise a persistent indexing daemon.

Who it’s NOT for

Teams seeking independently verified indexing accuracy, query latency or token savings from this review: our run measured none of those workloads.
Teams that cannot validate workspace changes: issue 673 remains open in the supplied extract and reports existing nodes retaining stale workspace IDs.
Buyers requiring a clean test-command result at the measured commit: our October 8 run exited with code 1, with the cause unresolved in the supplied tail.
Linux users who need custom tree-sitter grammars but cannot build from source: the installation guide says static Linux binaries skip those shared-object grammars.

Setup reality

In our recorded run on October 8, 2026, commit e12965558e80c153805521d174efcbda2b0654d5 completed dependency setup in 206 seconds and the build step in 445 seconds. The dependency summary recorded 417 packages. This does not establish that a release binary was installed on PATH or that an agent integration worked.

The sandbox configuration was 3 CPUs, 8 GB RAM and image golang:1.24-bookworm. The setup tail records downloading go1.27.0, so the image label is not proof that Go 1.24 performed the build. The installation guide requires Go 1.26+ and a C toolchain for source builds; it describes published binaries as self-contained.

The test command ran for 852 seconds and exited with code 1 without a harness timeout. Its parser summary recorded 206 successful and 8 failed package results, plus 43 packages without tests. These are recorded package-result counts, not individual test counts or independently reconciled exhaustive coverage. The available tail identifies internal/mcp as a failed package but does not show its failing assertion or explain all eight reported failures.

For a trial, verify the installed binary separately, configure the agent, start the daemon and check known queries in each repository. Linux users needing custom grammars should follow the source-build route.

Should you trial Gortex for agent context?

Gortex is worth evaluating if your coding agents need to follow relationships across repositories. The evidence here supports a successful source build and a reason to check workspace behavior carefully. It does not establish how accurately Gortex indexes your code or how much context it saves an agent.

The README describes a persistent SQLite graph containing functions, classes, call chains, HTTP routes and cross-service contracts. A daemon maintains the graph, and the CLI, MCP server, HTTP API and web interface expose it. This gives a team a concrete trial question: can graph queries recover the relationships its agents currently have to find by reading files?

The README advertises 257 languages or grammars and token reductions of up to 50 times per response. Those are project claims. We did not measure language coverage, token savings, indexing throughput or query latency. The README also gives differing agent-integration counts, so this review does not present one as a verified total.

What our October 8 run established

Our recorded run used commit e12965558e80c153805521d174efcbda2b0654d5, dated October 5, 2026. Dependency setup completed in 206 seconds, with 417 packages in the dependency summary. The build step succeeded in 445 seconds. These observations describe the source checkout and command steps; they do not verify a release installation, an installed CLI on PATH or a working MCP connection.

The recorded sandbox had 3 CPUs, 8 GB RAM and image golang:1.24-bookworm. The setup tail says go: downloading go1.27.0 (linux/amd64). Calling this a successful Go 1.24 build would therefore misrepresent the evidence. The checkout scan recorded 4,930 files, approximately 1,176,896 lines of source and 48.9 MB. Those are repository measurements, not release-binary size or indexing-workload results.

The test command ran for 852 seconds, exited with code 1 and did not hit the harness timeout. The parser summary recorded 206 successful and 8 failed package results, with 43 additional packages reporting no tests. Its total of 214 refers to the successful and failed package results. It is not a count of individual tests, and no complete-log reconciliation established unique, exhaustive coverage.

The supplied tail names github.com/zzet/gortex/internal/mcp as a failed package after 360.091 seconds. It does not show a failing assertion or explain the other reported failures. A nonzero test-command exit is a reason to investigate this commit in the intended environment, not proof that the CLI or graph engine is broken.

Installation has two distinct paths

The installation guide describes self-contained release binaries for Linux, macOS and Windows. Source builds require Go 1.26+ and a C toolchain because the tree-sitter bindings use CGO. The static Linux binary cannot load custom tree-sitter shared objects; the guide directs users who need those grammars to build from source.

Installing a binary is only the first check. Agent configuration, daemon startup, repository tracking and confirmation that the assistant actually calls graph tools are separate steps. Our recorded build does not demonstrate their completion.

Separate historical reports from current blockers

Search-truncation issue 672 reported that search_text silently capped results and their reported count. In the original report, a query returned 1,000 matches while git grep found 8,963. The supplied issue history now shows it closed as completed through pull request 845 on October 3, 2026. It should no longer be described as an open, unchanged defect. Closure does not establish that every released version contains the change or that all indexed searches match raw source search.

Workspace-scoping issue 673 remains open in the supplied extract. The reporter describes already-indexed nodes keeping their old workspace ID after a repository joins a shared workspace. Known text then returns count: 0. This is a reported failure on v0.63.7+0988412, not a behavior reproduced in our October run or established for every current build.

PDF-memory issue 676 is also historical rather than an unchanged open blocker. Its supplied history shows closure as completed through pull request 926 on October 19, followed by a referenced PDF extraction memory-and-work fix on October 20. Our October 8 run predates those events and did not index a PDF workload. Neither the old report nor its closure measures memory behavior in a current release.

A useful acceptance check

Choose a representative repository set and write down a few known symbols, callers and cross-repository relationships before indexing. Check those answers through the interface your agent will use. Then move an already-indexed repository into a shared workspace and repeat the checks. This directly addresses the remaining workspace report without assuming it occurs everywhere.

Keep ordinary source search available when completeness matters. Compare indexed and raw-search results with their exclusions in mind: a difference may reflect indexing policy rather than a query defect. Measure memory, query latency and agent context use separately if they determine whether adoption is worthwhile. None was measured in our run.

How to read the ratings

These are editorial evidence ratings on a 1-to-5 scale: 1 means little usable support in the supplied evidence; 2 means substantial unresolved limits; 3 means enough support for a controlled trial; 4 means detailed supporting evidence with limited gaps; 5 requires broad verification in the relevant category. Unknown adoption, compatibility or reliability cannot earn a high rating. The scores are not benchmark results or an overall production-readiness certificate.

Setup receives 3 because the source build succeeded and installation paths are documented, while installed-binary and agent checks remain unverified. Documentation receives 3 because the installation extract answers practical setup questions, but the README has inconsistent integration counts and most linked documentation was not supplied in full. Community receives 2 because issue discussion provides concrete reports and maintainer responses, but adoption and support responsiveness were not measured. Maturity receives 2 because workspace scoping remains an open report and the recorded test-command failures are unexplained, despite documented progress on other issues.

For adoption, start with the known-query checks and a separately verified installation. Expand the trial only after Gortex answers the relationships your agents need.

Alternatives

ProjectWhat it isPick it when
ZoektA source-code text search engine with substring and regular-expression matching across repositories.Choose it when your main requirement is indexed text search through commands, a web interface or an API. Its README supports that role; it does not establish exhaustive results for your corpus.
Aider gh↗A terminal AI pair-programming tool that makes a map of the codebase.Choose it when you want an editing assistant with repository context. This is a different workflow from evaluating a separate code-intelligence service.

What people are saying

  1. [github-trending] zzet/gortex

Sources

  1. Gortex README
  2. Gortex installation guide
  3. Silent search truncation issue
  4. Workspace scoping issue
  5. PDF memory issue
  6. Go indexing hang issue

More dev tools reviews