Skip to the card

2026-11-19 issue

Observed arrival · 2026-11-19

Wiredrag traces values across a codebase

wiredrag.systems Visit website
Editorial interest 82/100 Selection signal · not a rating of the site

An API for asking where a value travels through a repository, returning file-and-line locations plus places where tracing stopped.

Landing page captured for the 2026-11-19 issue.
For
Engineers tracing values across large codebases
Worth noticing
It marks traces “found” or “unconfirmed” and names files it did not read; the page says a question can take minutes.

Field notes

The homepage describes a workflow built around one repository commit and one question, with a stated ceiling of six million lines. Results are marked “found” or “unconfirmed,” and the page says it names files it did not read. Its comparison with grep and retrieval tools is unusually candid: ordinary single-file questions are explicitly called a poor fit, while the listed per-question prices vary between sections.

Observed signals

Read the marks

Editorial observations of this landing page, not a rating.

○OpenPublic substance visible
$PaidCommerce or pricing visible
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use

One card from the complete issue

Syntax in Assamese

364,042 arrived 1,000 judged 986 catalogued Enter the complete issue
wiredrag.systems

Landing page observed 2026-11-19. The live site may have changed.