Last verified: October 7, 2026
What You Can Now Do
Context Memo has split the research section apart: you can now access Simulator, Prompts, and Scans as distinct top-level tabs, with a new simulation button placed in the page header. Each tool is a first-class destination instead of a tab nested inside another tab. The practical change is where your attention goes when you open research. Before, you landed in one area and drilled down to find the tool you wanted. Now you pick the tool first, which means a scan review and a simulation run are two separate decisions instead of one navigation puzzle. If your team divides AI visibility work by function (one person owns prompt sets, another owns scan interpretation), each role now has a direct entry point rather than a shared starting screen.
Where It Is in Context Memo
The research section of the app. Simulator, Prompts, and Scans sit side by side as top-level tabs rather than nested under a single research view. The simulation button has moved out of the research area body and into the main page header row, so it stays visible regardless of which of the three tabs you have open.
How to Use It
- Open the research section. You'll see three tabs where there used to be one combined view: Simulator, Prompts, Scans. The tab you were last in is no longer buried a level down.
- Click the simulation button in the page header. Simulation starts from the header row, so you can launch one while reading a scan result without backing out to a different screen first.
- Go to Prompts to review and edit the prompt set you're tracking. This is the list of buyer questions your scans run against, now editable without passing through the scan view.
- Go to Scans to read how the models answered. Each scan result shows the answer text and which brands were named, so you can see where you appeared and where a competitor did instead.
- Go to Simulator to test a question before committing it to a tracked prompt set. Use it when you want a single read on model behavior rather than a recurring measurement.
- Hand off by tab. Point a teammate at Prompts or Scans directly instead of describing a click path through nested menus.
Why We Built It
Customers told us they wanted to find and launch research tools more quickly without navigating through nested menus. The nesting cost them time in the moment that mattered least: the minute between deciding to check something and actually seeing it. It also made the three tools look like one tool with three settings, which they are not. Prompts defines what you measure. Scans shows what the models said. Simulator is for a one-off read. Flattening the navigation makes that separation visible in the interface rather than something you learn after a few weeks of use.
The header placement for simulation follows the same logic. Running a simulation is an action you take in response to something you just read, often inside a scan result. Keeping the button in the header means the action is available from wherever you are in research, not only from the screen where simulation happens to live.
What It Does Not Do Yet
This release changes navigation and button placement. It does not change how scans run, how prompt sets are built, or what the models return. If you had a saved link or bookmark pointing into the old nested research view, update it to the new top-level tab. Team members who learned the previous click path will need one pass through the new layout, so flag it in your next internal standup rather than assuming the change announces itself.
The three tabs also remain separate surfaces rather than a single combined workspace. If your workflow is to read a scan, adjust a prompt, and rerun in one continuous motion, you will still move between tabs to do it. The header simulation button removes one of those hops, not all of them.