| What it is | A cloud agent for briefs, connected business apps and assignments that continue while you are away. | Agent software you operate, with configurable models, execution backends, persistent memory and reusable skills. |
|---|
| 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. | Open-source software with desktop and CLI options. Supported platforms and execution backends vary; this is an operated deployment, not a hosted-plan entitlement. |
|---|
| 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. | Local machine, containers, SSH or supported cloud backends. Jobs need the configured backend and gateway running; a sleeping local host is not always-on hosting. |
|---|
| 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. | MIT software is free. Budget for model/API subscriptions, tool services, hosting or hardware/electricity and maintenance. Optional Nous Portal bundles models and tools; some infrastructure costs remain separate. |
|---|
| 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. | Scheduled jobs, subagents and persistent Bot routines, with the appropriate running backend and gateway configuration. |
|---|
| 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. | Configurable browser automation, terminal/files, plugins and MCP. Backend and model endpoint choices determine where execution and data processing happen. |
|---|
| 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. | Local memory/profile files, session search and reusable skills; optional external memory providers. Check that requested memory writes occurred. Learning here is persisted context, not model-weight training. |
|---|
| 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. | Command approvals, allowlists and isolation options depend on operator configuration. Command matching is not an OS sandbox. Cloud model, tool and memory services have separate data policies. |
|---|
| 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. | Deployment, upgrades, secrets and uptime are your responsibility. A small local model is not equivalent to a frontier hosted one; evaluate the exact stack rather than the agent name alone. |
|---|