AG-UI & Agent UX
Phase 22Module 8 of 10
Shared State
Two tabs and a resume should not double-refund.
A lock on the filing cabinet plus a paper trail.
Visual Workflows
Start here — scroll inside each diagram frame to explore, then use + / − to zoom up to 200% if needed.
Overview
100%
Loading diagram...
Scroll inside the frame to explore · use + / − to zoom up to 200%
100%
Loading diagram...
Scroll inside the frame to explore · use + / − to zoom up to 200%
This turn
100%
Loading diagram...
Scroll inside the frame to explore · use + / − to zoom up to 200%
A lock on the filing cabinet plus a paper trail.
Key Takeaways
- 1.Shared state is the contract both UI and agent write.
- 2.Last-write-wins is usually wrong for approvals.
- 3.Do not put secrets in shared state.
- 4.Two tabs and a resume should not double-refund.
Real Example
Scenario
A lock on the filing cabinet plus a paper trail.
What you would do
In AG-UI & Agent UX, apply Shared State to this scenario: A lock on the filing cabinet plus a paper trail. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.
Cheat Sheet
Quick recap
quick ref- •Shared state is the contract both UI and agent write
- •Last-write-wins is usually wrong for approvals
- •Isolate per user and per run
Common Mistakes
- ✕Skipping evaluation for Shared State before production
- ✕No logging or tracing around shared state steps
- ✕Ignoring cost and latency implications