Assert Memory & List Bounds Memory
Two memory toggles — Assert Memory (Visual Assert) and List Bounds Memory (Scroll) — that reuse a recent result when the screen is unchanged instead of resolving from scratch. Both validate before reuse.
Two interactions have memory toggles distinct from Position Memory: Visual Assert uses Assert Memory, and Scroll uses List Bounds Memory. Both let Mavster reuse a recent result when the screen still matches, and fall back to a fresh resolution when it doesn't.
Assert Memory (Visual Assert)
The verbatim label and description in the editor:
Assert Memory
"Memorized asserts enabled. Cost savings and improved execution speed across runs. Automatically validates before use."
On by default. Repeated runs of the same assert on the same screen cost much less than cold-start runs. When off, every Visual Assert pays the full cost on every run.
List Bounds Memory (Scroll)
The verbatim label and description in the editor:
List Bounds Memory
"Skips the expensive list identification AI call when the screen looks the same."
On by default. When off, every Scroll step has to identify its target region from scratch.
When to turn them off
- Screens that change continuously — a feed of live content where the same assert finds different anchors each run.
- Lists with dynamically-loaded structure — infinite scrolls where the list bounds redraw as new content arrives.
- First-time debugging of a flaky step — disable to rule out stale memory, then turn back on once stable.
Cost framing
These two toggles together drive most of the cost gap between a fresh test and one that's been run a few times. Leaving both on is dramatically cheaper than leaving them off, with effectively no downside on stable screens.