What it means
The agent session decouples from the foreground UI: work continues with its own logs, tools, and time limits until done, failed, or cancelled.
Why designers should care
Background UX needs persistent status, push or in-app notifications on completion, readable summaries, and one-click open, not “come back and guess if it finished.”
Example
A cloud agent refactors twelve files over eight minutes; the user gets a bell notification, opens an activity summary with diffs, and approves merge from the receipt card.
Common mistakes
- Background jobs with no cancel or time cap.
- Completion with no summary. User must re-read entire chat to find outcome.
- Foreground and background agents conflicting on the same repo without warning.
Explore more
Frequently asked questions
What is Background Agent?
A background agent (or cloud agent) runs a task outside the active chat, on a remote VM, queued worker, or local process, while the user works elsewhere.
Why should designers care about Background Agent?
Background UX needs persistent status, push or in-app notifications on completion, readable summaries, and one-click open, not “come back and guess if it finished.”
What are common mistakes with Background Agent?
Background jobs with no cancel or time cap; Completion with no summary. User must re-read entire chat to find outcome; Foreground and background agents conflicting on the same repo without warning.