Saving frames completely does not mean stuffing them all into context. In the full scheme, after each action the framework by default shows the model only the last frame, while intermediate frames during the action are uniformly stored in the visual archive and actively retrieved only when the model needs them. The source believes this both preserves complete visual information and avoids a large number of historical images continuously occupying context space.
VISTA also introduces two text notes: GUIDE.md records rules and experience reusable across different levels, and WORKING.md records the current level's state, progress, and follow-up plans. When context approaches its limit, the model first organizes a handoff summary, then enters a new context window to continue the task, with the previous text notes, action history, and visual archive all preserved.
According to the execution flow described by the source, at the start of each episode the model first observes the current frame and available actions, combines prior experience to judge the environment state and propose action hypotheses; when information is insufficient, it calls tools to review historical frames, zoom into local regions, or even read pixel information to find evidence; after finding evidence, it first predicts the changes the operation may bring, and after the action is executed compares the actual result with the prediction, thereby correcting its understanding of the rules.
The key constraint here is: VISTA does not additionally train a new model. Environment understanding, action planning, and reasoning are still done by existing multimodal models; the Harness is only responsible for executing tool calls, saving visual history, and providing evidence when needed. As the source summarizes, what VISTA changes is not the model itself, but the way the model acquires, stores, and uses visual information.