| What it is | A cloud agent for briefs, connected business apps and assignments that continue while you are away. | Persistent named agents with role context, background work and repeatable routines on a shared cloud computer. |
|---|
| Can I use it? · documented | Research preview for US Pro/Max users invited from a waitlist. Not available to Team or Enterprise yet. Announced 21 October, with a safety update on 23 October. | Included on X Subscription Premium, Super and Ultra. Paid legacy Cursor/Teams and qualifying linked SuperGrok/X Premium+ accounts have other routes. Enterprise arrangements differ. |
|---|
| Where work runs · documented | Own cloud computer and browser; tasks continue after the app closes. The current preview cannot access files on your local computer. | Persistent cloud computer shared across the account's Bots. Optional Mac/Windows local command execution has its own permission policy; local execution does not imply local model processing. |
|---|
| How usage is paid for · documented | Included in Pro/Max during preview, sharing Claude's session and weekly limits. Background account checks consume that allowance. | Current X Subscription shares a weekly pool with Cursor and Grok, with prepaid top-ups. Legacy plans use Bot grants and optional Cursor-billed on-demand usage; linked grants do not stack. |
|---|
| What keeps running · documented | Morning briefs, account checks every few hours and longer tasks while you are away. It is not an immediate-response monitoring service. | Background work, scheduled routines, supported event triggers and handoffs between Bots. Verify that a specific connector supports the action your routine needs. |
|---|
| Browser and computer tools · documented | Connected apps/plugins and a cloud browser for other sites. You cannot watch or take over that browser yet; there is no model picker. | Browser, files, terminal, connected apps and human takeover. Optional local execution defaults to asking; websites can still block automated access. |
|---|
| What it remembers · documented | Claude memory, skills, connections and eligible past chats. Disconnecting an app does not erase what it learned; memory can be reset. | Per-Bot preferences, roles and conversation summaries. Working files, browser sessions and logins remain shared across the account. |
|---|
| Approvals and data boundaries · documented | Vendor describes consequential-action approvals, separate intent/privacy checks and isolated credential handling. Some actions remain prohibited despite approval; these controls are not a performance guarantee. | Auto Review and action rules; local policy defaults to asking. Requires storage, does not support Legacy Privacy Mode, and uses applicable Cursor training opt-out settings. |
|---|
| Decision-changing limits · documented | No Microsoft 365 yet, limited Slack functionality, no local files or browser takeover, and no outbound calls or SMS to others. Personal errands are less developed than work tasks. | Shared account state is not a per-Bot security boundary. Some unattended approval requests expire after about ten minutes without running; an unanswered request is not completed work. |
|---|