Repro Card Agent build log

A BYOK agent app for turning noisy bug evidence into coding-agent-ready repro cards.

Thursday, July 2, 2026Omid Saffari

Repro Card Agent is a one-page BYOK agent app for converting messy bug reports, QA notes, support tickets, and console traces into developer-ready reproduction cards.

The app is intentionally narrow. A visitor brings their own provider key, fills out the product surface, report, environment, logs, and preferred check style, then receives a copyable markdown handoff: readiness status, repro steps, evidence gaps, acceptance checks, and a starter Playwright test.

This is not an empty chat surface. The UI is a compact repro workbench with task-specific fields, readiness state, and a fixed output shape for coding-agent handoffs.

Why this release

Coding-agent workflows are only as good as the issue packets they receive. A support ticket that says "export is broken" usually needs one more pass before an agent or engineer can act on it safely: exact surface, expected and actual behavior, environment, log clues, and the smallest reproducible path.

Repro Card Agent packages that preparation step into a forkable BYOK app. The operator keeps the provider key, the project gets a better issue handoff, and the downstream coding agent gets a task that is closer to executable.

What shipped

  • Repo: https://github.com/dvnc-labs/repro-card-agent
  • Release: https://github.com/dvnc-labs/repro-card-agent/releases/tag/v0.1.0
  • Demo: https://repro-card-agent.vercel.app
  • Artifact type: BYOK agent app.
  • Scaffold: omidsaffari/ai-app-starter.
  • Runtime: Next.js 16, React 19, AI SDK v6 provider transport.
  • Default OpenAI path: Responses API via the starter model registry.
  • Provider options: OpenAI, Anthropic, and Google through visitor-supplied keys.
  • Standard package surface: README, code of conduct, contributing guide, changelog, and generated OG asset.

Trust boundary

The visitor key stays in browser session storage. It is sent only to the same-origin /api/run route as x-provider-key, used to construct the selected provider client for that request, and redacted from errors. There is no author-owned API key, no server-side fallback key, and no stored inference account.

The frozen starter trust-boundary files stayed untouched: src/lib/byok.ts, src/lib/secret.ts, src/app/api/run/route.ts, .github/workflows/ci.yml, and tests/byok.spec.ts.

Gates

  • Remote repo created from omidsaffari/ai-app-starter.
  • Local bun install: passed.
  • Local bun run lint: passed.
  • Local bun run typecheck: passed.
  • Local bun run build: passed.
  • Local BYOK no-leak Playwright smoke on PORT=3220: passed.
  • Runner package surface generated README/docs/OG files.
  • Runner gate repeated install, lint, typecheck, build, and Playwright: passed.
  • GitHub Actions CI on c37a934: passed.
  • GitHub release v0.1.0: published.
  • Production Vercel alias https://repro-card-agent.vercel.app: HTTP 200.

Release notes

The model slot now uses a repro-card system prompt and no image tool. The page was replaced with a two-pane repro workbench while preserving the starter BYOK transport and the stable Playwright test hooks. The package step generated the standard Omid Saffari Labs README, docs, and OG assets.

Distribution kit

Show HN title:

Show HN: Repro Card Agent - BYOK bug reports for coding agents

Targets:

  • Coding-agent and agentic engineering communities.
  • QA automation and Playwright users.
  • Support-engineering teams preparing issues for agent handoff.
  • BYOK AI app examples and AI SDK demo directories.
Last Updated

Jul 2, 2026

CategoryAgents

More from Agents

View all Agents articles
Newsletter

One letter, every week. Working systems — not hot takes.

Build logs, agentic engineering decisions, agent failures, evals, and what survives real users. Sent weekly, never more.

Weekly. No spam. Unsubscribe anytime.