RUNBRIDGEAG-UI / SDK MIGRATION
RUNBRIDGE / FIELD NOTES / 0.0.59 → 1.0.2

Return to the application after the replay.

The comparator observes client consumption. Your real signup, verification and resume screens remain a separate end-to-end check.

Reviewed October 15, 2026 · Pinned npm clients 0.0.59 and 1.0.2 · Original local fixtures

Use one owned test account and one question

For an application you operate, pick the workflow that changed during the SDK upgrade. For example, the agent begins onboarding, pauses while a user verifies an address, then resumes with a confirmation step. Write down the expected screen and state at each boundary before capturing events.

Reproduce with a fresh browser session

An existing session can skip the page you meant to test. WebTraceCheck is an optional way to open your own application in a fresh remote browser and inspect its signed-out UI, redirects and post-verification page. RunBridge does not launch that session, inspect its cookies or guarantee its browser or SDK build.

Use a disposable address only where it fits

If your owned test flow requires a non-sensitive email confirmation, the CleanTempMail web inbox can receive the test message manually. Follow the link or code in your actual app, then capture the resulting run. Use the website directly; this workflow does not require its paid API.

Do not use a disposable inbox for important account recovery or an essential production identity. AG-UI itself does not send mail, and a step named email-check is not proof that a message was delivered.

Separate the four observations

  1. The actual browser displayed the expected page.
  2. The optional test inbox received the expected confirmation.
  3. The captured producer emitted the relevant events.
  4. The pinned clients consumed those events in the way shown by the comparator.
↓ Synthetic email-check correlation example

In this original fixture, attemptRef is a correlation value that disappears from the modern subscriber until moved into metadata. It is intentionally synthetic. After applying the corresponding producer and subscriber change to your own app, repeat the real workflow and capture again.

Both linked services share this site’s project owner. They are optional related tools, not prerequisites for the comparator or independent endorsements of its results.