uTrace
For teams

The bottleneck was never talking to users.

It was tracing through a hundred transcripts to find one high-potential product change. uTrace spawns forward-deployed agents that do it for you — interviewing, building, validating, shipping.

Book a working sessionSee how it works
Four Discord messages converge on Archie. uTrace interviews the user one turn at a time, retrieves relevant product and code context, then prepares and checks an asynchronous implementation.

The whole feedback loop. Finally closed.

customer_opsCan we save this view?

Intake router

Active

Classify intent, then resolve the route

Classification probabilities

  1. Feature request92%
  2. Bug report6%
  3. Needs review2%

Resolved route

  1. Product Signal created
  2. Saved view attached
  3. Originating user invited

01

Signal, not noise

uTrace decides what deserves investigation before it creates work.

  1. Intent routingClassifies every message and routes it to the right path.
  2. Cross-signal corroborationWeighs multiple signals before creating any work.
  3. Sensitive-account policyBlocks or escalates requests that should never auto-execute.
/workspace

Browser observation

Structured

  1. DOM node (structured)

    role
    button
    name
    Save view
    state
    expanded false

  2. Interaction event

    type
    view_save_clicked
    target
    Save view

  3. API call (safe)

    method
    POST
    route
    /api/views
    status
    200
    time
    142ms

Trace

1234abcd5678ef90Live

Server span tree

  1. POST /api/views142ms
  2. ViewsController.create98ms
  3. ViewSerializer.capture41ms
  4. ViewService.create55ms
  5. DB: views (INSERT)37ms
W3C correlationTrace ID1234abcd5678ef90

02

See the workflow, not a screenshot

uTrace correlates what the user did with what the product and backend did.

  1. Structured DOM & accessibilityCaptures roles, names, and states—not pixels.
  2. Safe browser & API eventsRecords interactions and network calls without sensitive payloads.
  3. Correlated backend spansLinks every event to server traces using W3C trace context.

Evidence

142 events
Route
/workspace
Target
Save view
Trace
142 events · 2 backend spans · 1 user action

Current turn

ArchieSafe preview

“What should persist when you return?”

03

Ask while context is fresh

Archie turns observed behavior into short, human questions inside the user's workflow.

  1. Minimum-sufficient probingAsks only what is needed to reduce uncertainty.
  2. Speaks your languageUses the user’s terms, not trace jargon.
  3. One caption at a timeKeeps the focus on the current moment.

1 · User request

Source-linked
“Reopen the same saved view.”
Observed friction · repeated manual rebuild

2 · Success target

One behavior

BeforeRebuild every filter

AfterRestore exact view

3 · Implementation gate

Approved async

Only this evidence-backed scope can enter the workspace.

Evidence
PASSED
Scope
BOUNDED
Policy
ALLOWED

4 · Isolated build

Saved viewNot production
  1. 1− state = currentSession
  2. 2+ savedView = serialize(state)
  3. 3+ owner_id = :current_user
  1. TypecheckPASSED
  2. Unit testsPASSED
  3. Browser smokePASSED
PREVIEW READY FOR USER

04

Repair behind the gate

Only evidence-grounded, bounded work reaches an isolated asynchronous workspace.

  1. Evidence before codeChanges start only after checks confirm the case.
  2. Isolated, resumable workspaceWork happens off the live flow and can be paused or retried.
  3. Checks before previewRequired checks pass before any preview is shown.
DiscordTo: customer_ops

Your saved view preview is ready.

Re-open preview
app.local/previewCandidate ready
Saved view
Selected filtersRestoredView stateRestored
  • Filtered results
  • Applied scope
  • Evidence visible
ValidatedVALIDATION COMPLETE
Originating user
Today, 9:41 AM
“It remembers the exact view.”
USER CONFIRMED
Founder Packet
PUBLISHED
  • Requested change
  • Evidence summary
  • Validation note
GitHub PR
READY FOR REVIEW
Base: mainNOT MERGED

05

Bring the same user back

The originating user validates the preview before uTrace prepares a Founder Packet and PR.

  1. Same-user recontactuTrace re-invites the originating user to review the preview.
  2. Structured validationRecords validated, partially validated, not validated, or unclear.
  3. Human-owned mergeuTrace prepares the Founder Packet and PR set but never merges.

FROM FEEDBACK TO EVIDENCE

Scattered feedback. One coherent signal.

Users describe the same friction in different places, words, and tones. uTrace connects the evidence before it creates work.

DISCORDCommunity server

I rebuild this filter every Monday.

REDDITPublic forum

Why can't saved filters follow me between devices?

APP STOREApp review

Recreating the same segments is painful.

XSocial platform

Teams need reusable views.

ZENDESKSupport inbox

Can our team save and share this setup?

PRODUCT SIGNAL

Saved views

CORROBORATION
5 source-linked reports
PATTERN
Recurring workflow
NEXT
Invite to interview

Source-linked evidence

THE UTRACE SDK

Instrument once. Follow the evidence end to end.

One concise integration gives the preview runtime structured browser semantics, source redaction, and W3C-correlated server evidence without turning the product into a fake observability console.

01 · INTEGRATE

Describe the safe product surface once.

Register semantics, propagate an eligible trace, and record the milestone the interview can cite.

evidence.tsILLUSTRATIVE API
// illustrative APIsdk.registerTarget("save-view", { role: "button" })const trace = sdk.startTrace("view.save")trace.recordMilestone("view.saved")
LOCAL PROOFOne action, one correlated outcome
trace 4bf92f3577b34da6
  1. Browser actionsave-view · click
  2. Safe requestPOST /api/views · body redacted
  3. traceparent00-4bf92f35…-00f067aa…-01
  4. Server result201 · saved_views.insert · 238ms
  5. Evidence receiptbrowser + server correlated
  • Structured semanticsDOM, accessibility, route, and registered targets.
  • Redaction at sourceUnsafe values never enter the evidence buffer.
  • W3C correlationBrowser activity joins the exact backend trace.
  • Complete-path readinessMissing or uncorrelated components withdraw readiness.

START WITH ONE WORKFLOW

Your users already showed you the next change.

Bring one recurring product problem. uTrace connects the evidence, bounds the work, and returns a preview to the same user.

Book a working sessionExplore the product loop