Changelog
Product changes and what they mean for your workflow.
These notes describe implemented changes in the codebase. Dates are the recorded commit dates; availability in your workspace depends on deployment, access and configuration.
September 26, 2026 — Agent panel and theme switch
Dashboard screens gain an Agent panel: open it from the top bar to chat beside the screen you are viewing. Search Intelligence attaches the rows you are viewing, and a Site Health issue starts the panel with a question about it. The panel shares chats and outputs with the Agent workspace, and Open in Agent continues the same chat there.
The account menu’s theme checkbox is replaced by a one-click Light/Dark switch in the application and onboarding headers, and the dark theme moves to near-black neutrals.
For your team: ask about the screen you are on without leaving it, then move to the full workspace when the deliverable needs more room.
September 26, 2026 — One Agent capability
The unified Agent now uses one capability identity across access, model routing and usage configuration. This follows the consolidation of content and growth work into the Agent workspace.
For your team: use the Agent as the common place to investigate evidence and create reviewable deliverables. If a control is unavailable, check the displayed access or funding reason.
September 25, 2026 — Agent, Actions and reviewable outputs
A dedicated Agent workspace brings together new chats, Actions, Skills, Context and saved conversation history. Evidence handoffs let you begin with an existing finding instead of restating it.
Chats own a deliverable with revision history, user edits, copy and Markdown export. Long-form content requires outline approval before drafting. Runs expose distinct queued, running, cancelled, failed and limit-stop states.
For your team: choose a target, review its supporting evidence and refine the output before using it. The Agent does not publish or make external changes.
Work with outputs and revisions
September 25, 2026 — From implementation to measurement
Actions group related findings around a target and carry the work’s lifecycle. Explicit implementation declarations can reference the exact Agent output revision that was shipped.
Later evidence checks the expected outcomes of that declaration. The result distinguishes implemented work, work still being measured and work whose latest observation verified the expected checks. Search Demand connects actionable signals with their associated Action.
For your team: generating an output is separate from shipping it. Declare implementation after making the change, then review what later measurements support.
September 24, 2026 — Appearance and workflow refinements
The application and onboarding gained a device-local Light/Dark theme preference. Website page classification improved for product pages under category-style paths, alongside corrections to checkout, import and dialog behavior.
For your team: choose your preferred appearance; it is now a header switch (see September 26). For classification-dependent findings, inspect a later crawl’s page evidence rather than assuming old observations changed.
How to read these notes
A change in the product does not rewrite historical evidence. Audits, crawls, imported datasets and Agent revisions preserve the observations or work captured at the time.
When comparing before and after an update, keep measurement scope and availability in view. Contact support if your workspace’s behavior differs from the guide.