Topic
remote development
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-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-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-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
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
Sharing rust-analyzer across Git worktrees: in-memory overlay architecture and concurrency lessonsIn a multi-agent coding fleet, running separate rust-analyzer instances for every Git worktree multiplies memory consumption. Here is how an in-memory VFS overlay shares a single analysis database across worktrees, the Salsa concurrency traps we encountered, and our proposal to upstream.
6 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
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
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
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
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
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
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-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-25 · design note
Stop letting agents test in your working treeThe agent harnesses we run use the same loop: write a candidate fix into your checkout, run the tests, revert, try the next one. We moved that loop into overlay shadows of the mirrored workspace, mounted at the workspace's own path: candidates run in parallel and the checkout stays untouched.
7 min
2026-09-24 · notes
Where the milliseconds wentA 32-core node sitting at 2% load, a one-millisecond network, and half the queries taking 40 ms. Three things we found while measuring instead of guessing, including one optimisation that did not work and one that deadlocked.
7 min
2026-09-24 · design note
One terminal engine for the server, the Mac and the phoneProd keeps agents' terminals on a server and shows them on a Mac and an iPhone. Three emulators disagreed about the same bytes, so we replaced them with one Rust engine that moves its state instead of a picture of it.
11 min
2026-09-22 · design note
A mirror, not a mountThe analyzer runs on a node across the LAN and needs your code there. Not over a network filesystem, and not by uploading the tree every time: a manifest of hashes, a watermark per node, and a watcher that syncs only when something changed.
6 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


