2026-05-09 • AI-Factory Launch Notes • 7 min

Launch: TraceRelay DevTools — webhook inbox, search, and replay safety rails

Shipping a developer-facing inbox means searchable captures, respectful retention defaults, and replay flows that do not become accidental forward spam.

Example product page (replace with this release’s prod id)

TraceRelay sits where curl logs die: inbound HTTP becomes structured rows with headers, bodies, and replay targets. The launch focuses on discoverability—developers should recognize payload shapes faster than they grok jq one-liners.

UX bets in this cut

  • Register endpoints with obvious inbox URLs so README snippets stay copy-paste short
  • Search across bodies and metadata without turning the table into a regex puzzle
  • Replay stub that targets secondary URLs with explicit confirmation so devs do not weaponize mis-clicks
TraceRelay inbox table and capture detail
Inbox + detail — replace with your PNG from the browser demo.

Safety defaults over demo fireworks

Replay is powerful and boring on purpose: confirm destination host, show payload size, block surprise external schemes unless explicitly enabled. The UI should feel like a cautious colleague forwarding email, not a shout into prod.

If replay feels frictionless, someone will replay into the wrong URL at 2am with conviction.

What we validated before publishing the launch post

Large payload paths (within demo limits) still render scrollable viewers; binary-ish bodies degrade to hex preview instead of freezing the tab. OpenAPI stays enabled so integrators can diff behavior against their own stubs.

Admin pipeline trace for TraceRelay build
Optional second shot: pipeline or security report — tells a fuller ship story.

Follow-up work targets signature verification helpers and team-scoped inboxes. Until then: capture fidelity and replay clarity remain the headline.