Computer-Use Agents
Screen steps stored as diffs. Targets named by meaning, not coordinates.
memorable
$ memorable recall "reset the password in settings"
0.815 procedures/51ae9c3d-reset-password [lexical,semantic]
$ memorable show procedures/51ae9c3d-reset-password
Decisive steps last time:
1. [execute] Tap: "Change Password" button
A Computer-Use Agent Forgets
Every Screen It Crossed.
Match, Replay, Record.
Memorable keeps the path that worked and hands it back before the next run.
The current screen is matched against the stored one by what is on it, not by coordinates.
Each stored step names its target by meaning. A moved button still matches; a missing one stops the replay.
Only what changed on each screen is stored, so the procedure stays small.
memorable
$ memorable recall "export the Figma frame as PNG"
0.82 procedures/7d40c1be-export-frame
How It Works For Computer-Use Agents.
Phone and desktop traces come in through the device MCP. Screen states are stored as minimal diffs.
{ 01 }
Screens as diffs
Each step stores only what changed on screen.
What Memorable Reads.
3 CONFIGURED
Phone traces
Steps from the iOS device agent, joined to what each tap produced
Desktop traces
Steps from the desktop harness, same shape
The device MCP
Recall and show exposed to the agent as read-only tools
