22.3Near-Term (2026-2027)

Application Memory — the Open Frontier

What: A persistent model of the application — pages, flows, elements — that survives across agent sessions.

Why it matters: Today's agents rediscover your app every session. That's the single biggest economic inefficiency left in agent-driven testing: exploration tokens are spent re-learning what was known yesterday.

Who's building it: Vibium's Cortex (SQLite + sqlite-vec embeddings, graph pathfinding — "how do I get from login to settings?") is the clearest public articulation, still roadmap as of V1. Expect the major players to ship some form of app-map memory; whoever does it well changes the cost curve of exploratory agent testing.

Watch for: pathfinding across app graphs, automatic drift detection ("this page had 5 buttons, now 4"), and memory invalidation strategy (the hard part — stale memory is worse than no memory).

Passive Observation / Session Mining

Recording human sessions (Vibium's planned Retina extension; Meticulous and Checksum already mine session recordings commercially) to generate test scenarios from real user behavior. The privacy and data-governance questions are as hard as the technology.

Shared Browser Instances Between Humans, Agents, and Runners

Playwright's browser.bind() (v1.59) points the direction: the agent watches a human click through a flow (Screencast API), then acts in the same session. Expect "pair-testing with an agent" to become a normal workflow.