Current guide
Background jobs and notifications
Background jobs and notifications#
Some AI actions can leave their foreground progress view and continue as a background job. Workbench records accepted background work in its in-product Notification Center and, where supported, exposes completed work through AI Actions History or a report page.
Foreground progress#
The progress overlay belongs to the surface that started the action. An action launched from a full page can cover that page; an action launched in the sidebar remains constrained to the sidebar. Streaming-capable actions can update while text arrives, while other actions show staged progress and reveal the result only when complete.
Run in Background#
Choosing Run in Background closes the blocking progress surface without cancelling accepted work. Notification Center then shows progress and the final state. Notification Center is part of Workbench—it is not a promise of an operating-system or browser notification.
Stop and Cancel#
The initial Cancel control can change to Stop after work begins. Cancellation asks the client and service to stop, but it can race provider completion. If provider work or a usable result completed before cancellation took effect, the associated credit charge can remain.
Closing the tab or browser#
Background execution is not guaranteed to survive every extension or browser interruption. Accepted jobs record progress, but after an interrupted lifecycle Workbench must not present an unconfirmed action as successfully completed. Check Notification Center and AI Actions History after reopening.
Notification Center and AI Actions History#
- Notification Center shows activity and status updates.
- AI Actions History lists supported past actions and lets you revisit available outputs or reports.
- A report page is read-only evidence of a completed supported action; not every action produces one.
Related guides#
Guide feedback