FIELD NOTE / TIKTOK
Saved is not the same as survived.
The short film, the complete written thought, and the evidence behind it.
The TikTok edition will be linked here after its public post is verified.
Saved is not the same as survived.
Day 02 · 2026-09-29 · TikTok
Short video caption
A desktop agent's Saved toast is not a durability test. Close and relaunch under the target profile, then read the value from a fresh process. Simulated example. #EricFieldNotes
Full written post / accessible read
The agent changes a desktop app setting. A green Saved toast appears. It captures the screen and ends the run. Would you call that a pass if the app forgets the value on restart?
In this simulated run, the app writes to a temporary profile. It crashes before syncing the durable file. When another operator opens it, the setting is back. The agent's video looked flawless because it never crossed a restart boundary.
The harness records the target profile and expected value. After the agent finishes, it closes the app, relaunches under that profile, and reads the actual setting. A read-only config probe can corroborate it if the app exposes one.
When the user asked for a durable desktop change, require a restart and re-read before PASS. Fail if the value reverts or the restart probe is skipped. Do this because a toast is an acknowledgment of an interaction, not proof of persistence.
#EricFieldNotes
Evidence and boundary
On-screen boundary: SIMULATED DESKTOP TEST. The sources below support documented mechanisms and specifications; illustrative scenarios are not presented as measured incidents.