Topic
code intelligence
2026-11-06 · release
prod-code 0.3.52: read-only tools that say so, and failures that name the way onMore tools declare in the MCP catalog that they never write, shell and assembly files get outlines without a language server, and silent failures now explain themselves. Built and signed by a hosted workflow using Mitts; generated Rust commands still run cargo.
5 min
2026-11-06 · notes
Reverse Engineering with AI: Your Decompiler Can Lie to YouA field name, 2,000 look-alike functions and a wrong pseudo-C branch: an XRef walkthrough in which every conclusion is checked against machine instructions.
20 min
2026-11-05 · release
XRef 0.4.0: from serialized keys to the code that writes the fieldsUltra Blazing Fast XRef 0.4.0 adds xref field: give it the keys a stripped binary serializes, get field offsets with instruction evidence and ranked candidate writers. A recorded walkthrough on a synthetic test program, and the limits.
7 min
2026-11-03 · release
prod-code 0.3.49: several code reads in one MCP call, and edits that check what they replaceAn experimental code_workflow tool composes existing prod-code reads, previews and applies text edits only over the bytes it saw, and runs only checks it is asked for. It also fixes stalled refreshes in non-Git sessions. It makes no speed or context claim.
5 min
2026-11-03 · release
XRef 0.3.0: from a running process back to the instruction that wrote a fieldXRef 0.3.0 adds live inspection of Linux x86-64 processes and ties it to the same static analysis: find a value in memory, translate pointers to static addresses, count calls, and catch the store that changes a field. A recorded walkthrough on a stripped fixture, and the limits.
4 min
2026-11-02 · notes
57 seconds or 6 milliseconds: a first question to a stripped binaryOn one stripped Rust binary, a Ghidra 12.2 headless run (import, default analysis, one decompilation) took 57 to 59 s and found 1,123 of 2,096 function starts. Single xref commands took 2.5 to 6.4 ms and matched all 2,096. Plus two places where Ghidra is right and xref is not.
7 min
2026-10-27 · notes
The tree the node was buildingA remote build is only as good as the copy it builds. Three bug reports filed within one minute showed three ways the gateway's copy had drifted from the checkout: files cut by extension, directories that never went away, and a Swift package that never reached the Mac.
6 min
2026-10-21 · notes
The diff that was emptyTurning an associated function into a method is the mirror of making a method static, and the easier half. Writing it turned up something else: every write tool in the project reported an empty diff once it had applied its edit, because the old text was read after it was overwritten.
5 min
2026-10-19 · notes
Two conversions, three decisionsA type migration that writes .into() at every broken site sounds like the dangerous version. It holds up when the analyzer decides which conversions stay: only the ones that type-check and break nothing else are kept; the rest are taken back and left for a person. Type-correct, not judged right.
6 min
2026-10-18 · notes
The caller nobody editedA declaration edit can leave call text unchanged while breaking type inference. The original generify report illustrates why callers still need checking, and why failed caller discovery must stop the plan.
5 min
2026-10-17 · notes
Two negations, one meaningInverting a boolean predicate requires changing both its body and its uses. Three direct-call shapes explain the negations and parentheses; a September prod-code implementation also shows the limits of reference discovery and textual rewriting.
5 min
2026-10-14 · notes
The receiver that did somethingRemoving an unused receiver can still remove an evaluation at the call site. A September prod-code implementation blocked selected receiver shapes; its textual rule shows why type checks alone cannot establish that a rewrite preserves behaviour.
5 min
2026-10-13 · notes
The callers a return-type assist leaves behindA September rust-analyzer probe wrapped a function’s return type without updating its callers. The first prod-code implementation added propagation candidates and a report of unresolved calls. Its limits show why the caller side needs a separate check.
5 min
2026-10-12 · notes
What checking a fix revealedSeptember's prod-code fixes exposed a per-file exception that skipped its own case, a refusal that said too much, and an estimated cost replaced by a reported measurement. What those records teach about checking a fix.
4 min
2026-10-11 · notes
The function that was a fileChecking a proposed edit to a large file took half a minute, and running the check on sixteen threads changed almost nothing. The cause was a single function. Splitting it with the tool itself took the check to four seconds; the work turned up six bugs in the tool.
7 min
2026-10-11 · design note
Offloading the language server to a clusterA Swift subproject can sit inside a Rust checkout, and a validation request can disturb the engine answering navigation queries. How prod-code v0.3.29 chooses a compatible node and separates proposed edits from ordinary analysis.
4 min
2026-10-10 · notes
Every place a struct is builtTurning a value computed inside a method into a field is three small edits. The hard part is the third: finding every place the struct is built, among everything the analyzer calls a reference to it. Imports, return types and `Self` all qualify, and a pattern that lists every field breaks.
5 min
2026-10-09 · notes
The dry run someone else paid forA dry run is supposed to be the cheap step. Here it cost the next query, whoever asked it, twenty seconds. Moving validation onto a second analyzer fixed that, but the first measurement of the fix was taken on the wrong machine, and the second showed the cost had only moved.
8 min
2026-10-08 · notes
The errors were there before the editA new refactoring made a field private and rewrote every access to it, and its diff was right. Its verdict was 124 errors. The unchanged file reported the same 124, and every write tool had been counting them; our reading is that none of them was the edit's.
9 min
2026-10-07 · notes
The argument that landed in the wrong callFour bugs fixed in one afternoon, in the tools that write your code, and every one of them was a place where a tool took something on trust: a position, a write, a verdict, a line number. What each one did, how it was found, and what it checks now.
7 min
2026-10-06 · notes
A hundred and twenty-seven problems, three of them realChanging a type is the refactoring with the widest blast radius and the least help. Using the analyzer's diagnostics as the work list is the obvious design and it produced a report that was about 98 percent noise (124 of 127) - for a reason worth knowing about any tool built on an IDE's engine.
6 min
2026-10-05 · notes
The refactoring that changes nothingPromoting a magic value to a parameter is only safe if every existing caller keeps passing the value it had. That constraint is the whole design - and it is also why the tool refuses some extractions outright, and why the analyzer's answer to 'what function is this in' was the wrong question.
6 min
2026-10-04 · notes
Zero errors, and it did not compileEvery write tool in this series ends by saying the analyzer accepts the result. Building the one that bundles parameters into a struct produced a case where that sentence was printed and the code still did not build - and a four-line probe that says exactly how far the promise goes.
7 min
2026-10-04 · notes
Bloc Under the Microscope: What 67 Remote AST Tools Found Inside the Dart State Management EngineAnalysis of the reactive Dart state-management library created by Felix Angelov with prod-code: 45,736 lines across 616 files, event transformation pipelines, and test expectation matches.
5 min
2026-10-04 · notes
Broadway Under the Microscope: What 67 Remote AST Tools Found Inside the GenStage Concurrent Data PipelineDeep-dive analysis of dashbitco/broadway: 10,271 lines across 46 files, GenStage backpressure, dynamic batching, 435 word-matching assertion lines, and 18 raise lines.
5 min
2026-10-04 · notes
Composer Under the Microscope: What 67 Remote AST Tools Found Inside the PHP Dependency ManagerAnalysis of the PHP dependency manager Composer with prod-code: 139,690 lines across 634 files, a 12-node zero-edge dependency extraction, Boolean SAT resolution, 2-watched literal graphs, and 2,536 test assertion matching lines.
5 min
2026-10-04 · notes
Dart SDK Under the Microscope: What 67 Remote AST Tools Found Inside the Language Compiler and Analyzer EngineDeep-dive analysis of the official Dart SDK repository with prod-code: 5,741,847 lines across 25,732 files, Common Front End (CFE) Kernel AST compiler, analyzer Element model, 32,965 test asserts, and 8,678 invariants.
6 min
2026-10-04 · notes
Dio Under the Microscope: What 67 Remote AST Tools Found Inside the Dart HTTP ClientDeep-dive analysis of Flutter's premier HTTP networking engine with prod-code: 22,768 lines across 156 files, FIFO interceptor pipeline, platform adapters, and 845 test-assertion matching lines.
6 min
2026-10-04 · notes
DMD Under the Microscope: What 67 Remote AST Tools Found Inside the Reference D CompilerProfile of the reference D compiler with prod-code: 975,673 lines across 5,579 D files, an ImportC frontend that parses preprocessed C, a CTFE interpreter, and a dependency scan with one node.
6 min
2026-10-04 · notes
Elixir Under the Microscope: What 67 Remote AST Tools Found Inside the Macro Engine and Compiler PipelineDeep-dive analysis of elixir-lang/elixir: 390,071 lines across 780 files, quoted AST forms, protocol consolidation, 17,807 ExUnit assertions, and 632 error boundaries.
6 min
2026-10-04 · notes
Flutter Under the Microscope: What 67 Remote AST Tools Found Inside the Cross-Platform UI FrameworkAnalysis of the Flutter cross-platform UI framework with prod-code: 2,596,204 lines across 6,554 files, rendering pipeline, and test expectation matches.
7 min
2026-10-04 · notes
Homebrew Under the Microscope: What 67 Remote AST Tools Found Inside the macOS Package ManagerPackage-manager analysis for Homebrew by Max Howell and the maintainer team with prod-code: 371,069 lines across 2,379 Ruby files, Sorbet typing, and the FormulaInstaller bottle pipeline.
6 min
2026-10-04 · notes
Jekyll Under the Microscope: What 67 Remote AST Tools Found Inside the Classic Ruby Static Site GeneratorJekyll static-site generator analysis with 22,830 lines across 162 files, a six-stage pipeline, and test/error search counts.
5 min
2026-10-04 · notes
Laravel Under the Microscope: What 67 Remote AST Tools Found Inside the PHP Web Artisan FrameworkAnalysis of the Taylor Otwell web artisan PHP framework with prod-code: 573,479 lines of PHP, a four-node dependency extraction, recursive IoC container resolution, Eloquent ORM, and 34,633 test assertion matching lines.
5 min
2026-10-04 · notes
OpenResty Lua NGINX Under the Microscope: What 67 Remote AST Tools Found Inside Cosockets and Execution ContextsDeep-dive architectural analysis of openresty/lua-nginx-module: 224,672 lines across 434 files, non-blocking cosocket yielding, NGINX execution contexts, 6,770 assertion-section matching lines, and 827 NGX_ERROR token occurrences.
6 min
2026-10-04 · notes
Luau Under the Microscope: What 67 Remote AST Tools Found Inside the Gradual Type Checker and Native CodeGenDeep-dive analysis of luau-lang/luau: 534,195 lines across 1,533 files, deferred constraint resolution, optional native codegen, 16,270 test-assertion matching lines, and 1,822 invariant assertions.
7 min
2026-10-04 · notes
Mastodon Under the Microscope: What 67 Remote AST Tools Found Inside the Federated ActivityPub EngineAnalysis of the federated ActivityPub engine developed by Eugen Rochko and the Mastodon community with prod-code: 189,749 lines across 3,278 files, ActivityPub verification, and 8,191 RSpec expectation matches.
5 min
2026-10-04 · notes
Neovim Under the Microscope: What 67 Remote AST Tools Found Inside the Lua Subsystem and Built-in LSP ClientDeep-dive analysis of Neovim's modern Lua architecture with prod-code: 448,172 lines across 854 files, asynchronous LSP client, incremental document synchronization, and reproducible source-pattern counts.
5 min
2026-10-04 · notes
Nim Under the Microscope: What 67 Remote AST Tools Found Inside the Self-Hosted Metaprogramming CompilerHistorical Nim compiler analysis with prod-code: 460,749 lines of Nim, multi-backend code generation, allocator test clone clusters, 1,824 invariant asserts, and a reported 94% AST slice reduction.
3 min
2026-10-04 · notes
Nimble Under the Microscope: What 67 Remote AST Tools Found Inside the Nim Package ManagerAnalysis of Nim's package manager and build orchestrator with prod-code: 38,910 lines of Nim, a dependency scan that recognized no modules, SAT-based dependency resolution, and compiler AST declarative parsing.
4 min
2026-10-04 · notes
Nimbus Under the Microscope: What 67 Remote AST Tools Found Inside the Ethereum Consensus ClientHistorical Nimbus consensus client analysis with prod-code: 179,711 lines of Nim, hard-fork specification clones, and 585 Result type matches.
4 min
2026-10-04 · notes
Phobos Under the Microscope: What 67 Remote AST Tools Found Inside the D Standard LibraryAnalysis of the D standard library with prod-code: 366,399 lines of D, a dependency scan that recognized no modules, range-based algorithms, Design by Introspection, and repository-wide matching-line counts for assertions and unittest occurrences.
4 min
2026-10-04 · notes
Phoenix LiveView Under the Microscope: A Source Review of the Server-Driven UI and Diff EngineDeep-dive analysis of phoenixframework/phoenix_live_view: 142,201 lines across 430 files, HEEx compile-time template splitting with runtime diffing, websocket state machines, 3,451 word-matching assertion lines, and 215 raise lines.
6 min
2026-10-04 · notes
Phoenix Under the Microscope: A Source Review of the Web Framework and Real-Time EngineDeep-dive analysis of phoenixframework/phoenix: 100,976 lines across 508 files, generated route matching, channel multiplexing, and reproducible text-match counts.
5 min
2026-10-04 · notes
Rails Under the Microscope: What 67 Remote AST Tools Found Inside the Ruby Web FrameworkRails framework analysis with 3,478 Ruby files, Active Record queries, component packages, and test/error search results; subsystem line subtotals are withdrawn due to a discrepancy.
6 min
2026-10-04 · notes
Symfony Under the Microscope: What 67 Remote AST Tools Found Inside the Enterprise PHP Component MonorepoAnalysis of the enterprise PHP component ecosystem created by Fabien Potencier with prod-code: 2,201,262 lines across 11,999 files, a 64-node zero-edge dependency extraction, ahead-of-time compiled DI passes, and 47,912 test assertion matching lines.
5 min
2026-10-04 · notes
Vibe.d Under the Microscope: What 67 Remote AST Tools Found Inside the D Asynchronous Web FrameworkAnalysis of the D asynchronous web framework with prod-code: 30,151 lines across 108 files, a two-node dependency extraction with no edges, compile-time REST interface generation, and repository-wide assertion matching lines.
5 min
2026-10-04 · notes
WordPress Under the Microscope: Selected Results from a 67-Tool AST Suite on the Web Publishing EngineHistorical WordPress 6.8 source analysis with prod-code: 673,853 lines across 1,899 PHP files, WP_Hook dispatch, and a 693-node dependency extraction with no detected edges.
6 min
2026-10-04 · notes
ZLS Under the Microscope: What 67 Remote AST Tools Found Inside the Zig Language ServerHistorical ZLS analysis with prod-code: 56,190 lines of Zig, LSP protocol decoupling, completion test clone clusters, 86 errdefers, and an in-memory refactoring pre-flight check.
4 min
2026-10-03 · notes
The refactoring that is mostly importsMoving a function to another module is cut and paste and then an unbounded amount of fixing every file that imported it. Building the tool that does both, and the two bugs that made it quietly skip the second.
7 min
2026-10-03 · notes
TigerBeetle Under the Microscope: What 67 Remote AST Tools Found Inside the Distributed Financial Accounting DatabaseHistorical TigerBeetle analysis with prod-code: 8,251 invariant asserts, consensus message frames, zero-allocation invariants, and an in-memory ZLS refactoring pre-flight check.
5 min
2026-10-02 · notes
A killed process writes no profileCoverage went from 53% to 87% and every file in the coverage report crossed 80%. Three things cost a day each: a SIGKILL that silently erased a whole daemon's coverage, a test that passed by skipping, and a read with a deadline it never checked.
9 min
2026-10-02 · notes
Outside any functionIn a mixed Go/JavaScript checkout, impact analysis reported zero changed functions and claimed every edit fell outside all functions. Why root manifests blind polyglot analyzers, how arrow functions hide from LSP kinds, and why missing symbols must be a gap rather than a verdict.
3 min
2026-10-01 · notes
One field, three spellingsCross-language schema rename needs semantic edits for identifiers and separate text edits for wire names. A polyglot fixture shows how prod-code plans the change, validates it, and reports what remains.
7 min
2026-10-01 · design note
Language detection: what sixty test cases proveprod-code v0.3.19 expands workspace detection, but a detected language is not proof of semantic support. The marker matrix and release artifacts show what the version provides.
4 min
2026-09-30 · notes
The refactor no tool ownsRename is everywhere; changing what a function takes is nowhere. Building it meant letting the declaration write the rule, checking the result against the analyzer's own reference list, and refusing, under a normal apply, to write what the analyzer rejects.
6 min
2026-09-30 · notes
1,485 Error Checks and Zero Import Cycles: Dissecting Prometheus's 84-Package Engine with 67 AST ToolsWe benchmarked all 67 prod-code AST tools against prometheus/prometheus: 385K lines of Go, 84 packages, 1,485 error checks, 99% slicing reduction, and Bug #740 fixed in remote module dependencies.
11 min
2026-09-30 · notes
204 Code Clones and Two Self-Loops: Dissecting Bevy's 97-Crate Engine with 67 AST ToolsWe benchmarked all 67 prod-code AST tools against bevyengine/bevy: 661K lines of Rust, 97 crates, 204 exact code clones, 2 dev-dependency loops, and Bug #739 discovered and fixed in fast-sync.
12 min
2026-09-30 · notes
347 Code Clones and a Self-Loop: Breaking Down uv's 74-Crate Workspace with 67 AST ToolsThe author's report of running the prod-code AST tool suite against astral-sh/uv: 559K lines of Rust, 74 crates, 347 reported duplicated test-fixture occurrences, a self-referential cycle in uv-preview, and Issue #738 resolved in fast-sync.
12 min
2026-09-30 · notes
5.3 Million Lines of Go and 779 Packages: Dissecting Kubernetes with 67 AST ToolsWe benchmarked all 67 prod-code AST tools against kubernetes/kubernetes: 5.38M lines of Go across 17,823 files, 779 packages, a reported but unmeasured 0% laptop CPU, and fixed Bugs #741 and #742 in Go signature compilation and predicate inversion.
11 min
2026-09-30 · notes
Alamofire Under the Microscope: What 67 AST Tools Found Inside the Swift Networking EngineWe benchmarked all 67 prod-code AST tools against Alamofire: 39,000 lines of Swift, 92 throw sites (tests included), 20 clone groups, and remote Apple Silicon test offloading.
5 min
2026-09-30 · notes
Arrow Under the Microscope: What 67 Remote AST Tools Found Inside Kotlin's Functional CoreWe evaluated prod-code AST tools against arrow-kt/arrow: 72,889 lines of Kotlin across 757 files, 38-module Gradle architecture, structural search for the Raise DSL, and cluster-verified AST refactoring.
5 min
2026-09-30 · notes
ASP.NET Core Under the Microscope: What 67 Remote AST Tools Found Inside Microsoft's Web EngineWe evaluated prod-code AST tools against dotnet/aspnetcore: 1,757,169 lines of C# across 10,685 files, 625 projects in a single repository, Roslyn generator snapshot clones, and cluster-verified OmniSharp refactoring.
5 min
2026-09-30 · notes
BenchmarkDotNet Under the Microscope: What 67 Remote AST Tools Found Inside the .NET Micro-Benchmarking EngineWe evaluated prod-code AST tools against dotnet/BenchmarkDotNet: 120,810 lines of C# across 1,175 files, 29 projects in an acyclic DAG, 1,120 benchmark harnesses, and cluster-verified OmniSharp refactoring.
7 min
2026-09-30 · notes
Black Under the Microscope: What 67 AST Tools Found Inside Python's Uncompromising FormatterWe benchmarked all 67 prod-code AST tools against psf/black: 135K lines of Python, 12-callsite parameter object bundling across 4 files, import cycle detection in concurrency, 99.8% slicing reduction, and a predicate inversion refused over a non-call reference.
7 min
2026-09-30 · notes
curl Under the Microscope: What 67 AST Tools Found Inside the Ubiquitous Transfer EngineWe benchmarked all 67 prod-code AST tools against curl/curl: 200,000 lines of C, 1,924 failf/infof logging call sites, and parameterized AST codemod previews.
4 min
2026-09-30 · notes
Detekt Under the Microscope: What 67 Remote AST Tools Found Inside Kotlin's Static Code AnalyzerWe evaluated prod-code AST tools against detekt/detekt: 132,028 lines of Kotlin across 1,105 files, 41-module Gradle architecture with 4 test cycles, structural search across 31 files, and cluster-verified AST refactoring.
6 min
2026-09-30 · notes
DuckDB Under the Microscope: What 67 AST Tools Found Inside the Analytical EngineWe benchmarked all 67 prod-code AST tools against duckdb/duckdb: 681,000 lines of modern C++, QueryResult slicing, and catch2 matcher guardrails.
5 min
2026-09-30 · notes
EF Core Under the Microscope: What 67 Remote AST Tools Found Inside .NET's Relational EngineWe evaluated prod-code AST tools against dotnet/efcore: 1,749,818 lines of C# across 5,778 files, 58-project acyclic architecture, Northwind clone clusters, and cluster-verified OmniSharp refactoring.
7 min
2026-09-30 · notes
etcd Under the Microscope: What 67 AST Tools Found Inside Cloud-Native ConsensusWe benchmarked all 67 prod-code AST tools against etcd-io/etcd: 220K lines of Go, zero cyclic dependencies across 1,094 files, 99.9% slicing reduction on Raft leadership transfers, 445 structural error returns in 1.2s, and interface contract safety refusals.
8 min
2026-09-30 · notes
Express Under the Microscope: What 67 AST Tools Found Inside the Node.js BackboneWe benchmarked all 67 prod-code AST tools against expressjs/express: 21,000 lines of JavaScript, request-dispatch search and slicing, and prototype guardrails.
4 min
2026-09-30 · notes
FastAPI Under the Microscope: What 67 AST Tools Found Inside Python's Modern Async FrameworkWe benchmarked all 67 prod-code AST tools against tiangolo/fastapi: 118K lines of Python, 135-occurrence OpenAPI clone groups, 99.8% slicing reduction on dependency solving, parameter object bundling, and classmethod safety refusals in method extraction.
6 min
2026-09-30 · notes
Flask Under the Microscope: What 67 AST Tools Found Inside Python's Iconic MicroframeworkWe benchmarked all 67 prod-code AST tools against pallets/flask: 18K lines of Python, blueprint static file clone clusters, 98.6% slicing reduction on request dispatch, dataclass parameter object bundling, and property safety refusals in boolean inversion.
6 min
2026-09-30 · notes
Ghostty Under the Microscope: What 67 Remote AST Tools Found Inside the High-Performance Terminal EmulatorHistorical Ghostty terminal emulator analysis with prod-code: Zig source counts, VT test clones, cleanup patterns, and a ZLS refactoring limitation. Native applications support macOS and Linux.
4 min
2026-09-30 · notes
Git Under the Microscope: What 67 AST Tools Found Inside the Core VCSWe benchmarked all 67 prod-code AST tools against git/git: 443,000 lines of C, 4,657 die() and error() call sites, and multi-file structural codemods.
3 min
2026-09-30 · notes
Guava Under the Microscope: What Remote AST Tools Found Inside Google's Java CoreWe benchmarked prod-code AST tools against google/guava: 795,118 lines of Java, 5-module DAG resolution in 100ms, and 33-occurrence clone analysis.
5 min
2026-09-30 · design note
Half a Million Lines of Arrow: What 67 AST Analyzers Found Inside Polars' Query EngineWe pointed all 67 tools of prod-code at pola-rs/polars on an idle 32-core cluster node. 526K lines of Rust across 33 crates, 4 reported cycles that are dev-dependency edges, catching a UTF-8 non-char-boundary tokenizer panic, in-memory RAM validation, and 36-test remote execution.
16 min
2026-09-30 · notes
Half a Million Lines of Python and 25 Import Cycles: Dissecting Django with 67 AST ToolsWe benchmarked all 67 prod-code AST tools against django/django: 527K lines of Python across 2,932 files, 25 circular check paths, 99.9% slicing reduction, and safety refusals and previews in Python predicate inversion and parameter bundling.
9 min
2026-09-30 · notes
Kafka Under the Microscope: What 67 Remote AST Tools Found Inside the Distributed Event CoreWe benchmarked prod-code AST tools against apache/kafka: 1,717,457 lines across 6,218 Java and 257 Scala files, 64-module DAG resolution, and 125-occurrence data-object clone analysis.
6 min
2026-09-30 · notes
Kotlinx.coroutines Under the Microscope: What 67 Remote AST Tools Found Inside Kotlin's Concurrency RuntimeWe evaluated prod-code AST tools against Kotlin/kotlinx.coroutines: 113,379 lines of Kotlin across 1,039 files, 25-module dependency report with no cycles among 22 extracted edges, structural pattern search across 42 files, and cluster-verified AST refactoring.
6 min
2026-09-30 · notes
Ktor Under the Microscope: What 67 Remote AST Tools Found Inside Kotlin's Asynchronous Web FrameworkWe evaluated prod-code AST tools against ktorio/ktor: 295,995 lines of Kotlin across 2,423 files, 134-module Gradle KTS architecture with 100 extractor-reported module cycle paths, and cluster-verified AST refactoring.
6 min
2026-09-30 · notes
Moby Under the Microscope: What 67 AST Tools Found Inside Docker's EngineSelected results from the 67-tool prod-code AST suite on moby/moby, as reported: 387K lines of Go, 224 Protobuf varint clone occurrences, 99.9% slicing reduction on ContainerStart, 858 structural error returns in 1.9s, and a reported rejection during boolean inversion.
6 min
2026-09-30 · notes
Netty Under the Microscope: What 67 Remote AST Tools Found Inside Java's High-Throughput I/O EngineWe benchmarked prod-code AST tools against netty/netty: 652,153 lines across 3,595 Java files, 61-module graph analysis reporting an all-to-bom metadata-reference cycle, and 510-occurrence Huffman lookup tables.
6 min
2026-09-30 · notes
Next.js Under the Microscope: What 67 AST Tools Found Inside the React FrameworkSelected results from the 67-tool prod-code AST suite on vercel/next.js, as reported: 1.2M lines of TypeScript, SSR render pipeline slicing, and cross-file boolean inversions.
3 min
2026-09-30 · notes
Apache Pekko Under the Microscope: What 67 Remote AST Tools Found Inside the High-Throughput Actor RuntimeHistorical Apache Pekko actor runtime analysis with prod-code: Scala and Java source counts, 41 extracted SBT modules, 3.5% reported clone density, and a remote Metals refactoring example.
6 min
2026-09-30 · notes
Play Framework Under the Microscope: What 67 Remote AST Tools Found Inside the High-Velocity Web EngineHistorical Play Framework analysis with prod-code: Scala and Java source counts, 44 extracted SBT modules, form and router clones, and a remote Metals refactoring example with verification limits.
5 min
2026-09-30 · notes
React Under the Microscope: What 67 AST Tools Found Inside the UI EngineSelected results from the 67-tool prod-code AST suite on facebook/react, as reported: 745,000 lines across 4,445 files, Fiber work loop slicing, and compiler generic guardrails.
3 min
2026-09-30 · notes
Redis Under the Microscope: What 67 AST Tools Found Inside the In-Memory EngineSelected results from the 67-tool prod-code AST suite on redis/redis, as reported: 211,000 lines of C, event loop slicing down to epoll_wait, and static non-call guardrails.
3 min
2026-09-30 · notes
Roslyn Under the Microscope: What 67 Remote AST Tools Found Inside the C# CompilerWe evaluated prod-code AST tools against dotnet/roslyn: 6,499,949 lines of C# across 18,176 files, 394 projects, 15,300+ assertion calls, and an OmniSharp extraction whose published helper does not compile.
5 min
2026-09-30 · notes
Scalameta Under the Microscope: What 67 Remote AST Tools Found Inside the Scala Metaprogramming PlatformHistorical Scalameta Scala metaprogramming analysis with prod-code: 106,270 Scala and Java lines, 24 extracted SBT modules, 202 reported @ast declarations, and a remote Metals refactoring example.
5 min
2026-09-30 · notes
Apache Spark Under the Microscope: What 67 Remote AST Tools Found Inside the 2-Million-Line Distributed EngineHistorical Apache Spark analysis with prod-code: Scala and Java source counts, 52 extracted modules, 0.7% reported clone density, and a remote Metals refactoring example with verification limits.
5 min
2026-09-30 · notes
Spring Boot Under the Microscope: What 67 Remote AST Tools Found Inside the Enterprise Java StandardWe ran prod-code AST tools against spring-projects/spring-boot, as reported: 880,132 lines of Java, 448 Gradle modules with zero reported cycles in the extracted graph, and 55-occurrence autoconfiguration duplication.
4 min
2026-09-30 · notes
Swift Algorithms Under the Microscope: What 67 AST Tools Found Inside Apple's Sequence EngineSelected results from the 67-tool prod-code AST suite on apple/swift-algorithms, as reported: 13,700 lines of Swift, 81 bounds invariants, and remote Apple Silicon test offloading.
3 min
2026-09-30 · notes
Swift Argument Parser Under the Microscope: What 67 AST Tools Found Inside Apple's CLI FrameworkSelected results from the 67-tool prod-code AST suite on apple/swift-argument-parser, as reported: 30,000 lines of Swift, 64 matched throw sites, and remote Apple Silicon test offloading.
4 min
2026-09-30 · notes
Swift Collections Under the Microscope: What 67 AST Tools Found Inside Apple's Data Structure EngineSelected results from the 67-tool prod-code AST suite on apple/swift-collections, as reported: 71,000 lines of Swift, 1,279 matched assert and precondition calls, and remote Apple Silicon test offloading.
4 min
2026-09-30 · notes
TypeScript Under the Microscope: What 67 AST Tools Found Inside the CompilerSelected results from the 67-tool prod-code AST suite on microsoft/TypeScript, as reported: 264,411 declarations across 31,433 files, AST clone clusters, transitive slicing, and compiler in-memory validation.
4 min
2026-09-30 · notes
Zig Under the Microscope: Selected Results from a 67-Tool AST Suite on the Self-Hosted Compiler and Standard LibraryHistorical Zig compiler and standard library analysis with prod-code: source distribution, x86_64 codegen clones, errdefer patterns, and a remote ZLS refactoring example. Zig is now hosted on Codeberg.
7 min
2026-09-29 · notes
Hover lies by omissionA struct with eleven fields shows ten, so any test value built from that answer is missing one, and the only hint is an ellipsis the agent ignored. What it takes to generate a fixture you can trust: read the declaration rather than the summary, and type-check the result before handing it over.
7 min
2026-09-29 · design note
7,156 Cyclic Module Paths: Stress-Testing Tantivy's Search Engine with 67 AST ToolsWe subjected quickwit-oss/tantivy to all 67 prod-code tools on an idle 32-core cluster node. Reported results: 7,156 module cycle paths, 18-file AST renames, clone detection in JIT expressions, and safe-delete invariants.
17 min
2026-09-29 · notes
What our ripgrep report can and cannot showWe reassessed our September ripgrep report. Its published excerpts do not substantiate the claimed tool coverage or speedups; issue #735 documents a narrower failure in prod-code.
5 min
2026-09-29 · design note
Six Circular Dependencies in Tokio: What 67 AST Analyzers Found Inside Rust's Async EngineWe pointed all 67 tools of prod-code at tokio-rs/tokio on an idle 32-core cluster node. From 6 reported dependency cycle paths and silent Deref evaluation ordering traps to an unhandled sysroot crash on Box-here is what happened.
19 min
2026-09-28 · notes
The files are not the answerAn agent asked to change one function opens three files and spends most of its context on code that has nothing to do with the task. A slice is the other shape of the same question: the declarations the function depends on, and nothing that merely lives beside them.
8 min
2026-09-27 · notes
Both bugs said no matchesA structural rewrite that found nothing, twice, for two unrelated reasons in two different layers. What it takes to tell an empty answer from a broken one, and why the fix was tracing rather than thinking harder.
6 min
2026-09-26 · design note
Your comments are the search indexAn agent that knows what it wants but not what it is called has nothing to ask. We gave it a question box, then looked at what the answers tracked in a five-question sample: not the ranking, which was the same everywhere, but the prose your team did or did not write above each function.
9 min
2026-09-23 · design note
The analyzer already knows your patch is brokenAn agent writes a file, runs a build, reads the errors and tries again. The database that answered its last hover could have told it in 100 ms, without writing anything. What that takes, and the one error class the rust-analyzer build we embed stayed silent about.
6 min
2026-09-22 · design note
Never grep for a line number againLSP is positional: to ask who calls a function you must first know its file, line and column. Agents get that by grepping, and grep does not know what a symbol is. We made every tool take the name instead.
5 min
2026-09-21 · design note
Salsa has no branchesTwo agents on two worktrees of one repository, sharing one analyzer database, answer each other's questions. A benchmark that forks four worktrees and asserts what each should see, and why we stopped trying to share anything writable.
7 min
2026-09-21 · design note
Your laptop is the wrong place for rust-analyzerTen coding agents in ten worktrees means ten analyzers and ten cargo builds on one machine. We moved the analyzer, the builds and the tests to Linux nodes on the LAN, mirror the checkout there by content hash, and let the laptop do the one thing it is good at: editing.
7 min





