SovereignStack Inventory Sale

Developer Tools

repo-recon

Available

A CLI that probes a running web app and writes a reusable context packet: screenshots, route/DOM metadata, timings, JavaScript errors, and network calls. Built for handoffs where code without behavior is incomplete.

A tooling buyer or agency gets a repeatable `npx` workflow that produces a `.repo-recon/` packet humans and coding agents can actually use.

Contact for pricingCommercial source license · Exclusive acquisition1 screenshot

Build vs buy

Avoid writing Puppeteer capture, framework-aware route discovery, and a stable packet format that another team can consume.

Differentiation

Combines live screenshots with runtime signals (errors, network, timings) in one repo-local packet — not a full crawler and not a production APM.

Best fit

Developers, agencies, and tooling vendors who want repeatable visual/runtime context for AI coding agents or human handoffs.

Evidence

Screenshots are the working interface — not a pitch deck. Click to enlarge.

Click any image to open the gallery. Use arrow keys in the lightbox.

Why it matters

Source explains structure. It does not show what the running app looks like, which routes 500, or which API the homepage actually calls. repo-recon captures that missing half.

What it does

Point repo-recon at a live app. It discovers routes, captures pages and runtime signals, and writes a portable packet inside the repository.

Operational advantage

Compresses the “spin it up and click around” hour that happens at the start of every unfamiliar frontend. Especially valuable where AI agents are now part of the handoff.

Build vs buy

Avoid writing Puppeteer capture, framework-aware route discovery, and a stable packet format that another team can consume.

Interface advantage

Zero-config CLI. Point it at a live local or remote app; it does not ask the operator to become a browser-automation engineer.

What makes this different

Combines live screenshots with runtime signals (errors, network, timings) in one repo-local packet — not a full crawler and not a production APM.

Where this gets used

  • Attach visual/runtime evidence to a repo before an agent session
  • Handoff a running app to a contractor without a Zoom tour
  • Capture regressions as packets, not Slack screenshots

Commercial paths

  • Commercial license for agency standard kits
  • Embed in an internal platform or AI coding product
  • npm-distributed developer utility with support retainers

Best buyer fit

Developers, agencies, and tooling vendors who want repeatable visual/runtime context for AI coding agents or human handoffs.

Current status

Available for commercial licensing or exclusive acquisition. Requires a running app and downloads Chromium on first use.

Key capabilities

  • Screenshots plus DOM/navigation metadata
  • Timing data, JavaScript errors, and API/network calls
  • Framework-aware route discovery
  • Chromium/Puppeteer capture
  • npx workflow writing a `.repo-recon/` packet

Related inventory