Research · The host is the plot
Persistent computer
Last updated: 2026-08-12
What “persistent cloud computer” actually means
❓ Is the scarce object a durable VM, a session sandbox, a user laptop, or rented inference?
Grok Bot’s load-bearing sentence is: work happens on a computer that is not your laptop, and that computer does not stall when you step away.[1][3]
Official mechanism (not the ads):
- Each member gets one dedicated managed Linux virtual machine.[5]
- All of that member’s Bots share it. Files, browser cookies, signed-in sessions, and command-line credentials are account-scoped, not Bot-scoped.[2][3]
- Each Bot gets its own screen so they can click in parallel. Screens are not separate security boundaries.[2][3]
- Durable project files live at
/workspace. Temporary directories and manually installed packages are replaceable. Updates/recover can preserve “durable state”; Reset can discard recent unsaved work.[3] - You can watch via Agent Computer, take over for passwords / 2FA / CAPTCHA / payments, then return control. Do not paste secrets in chat.[3][19]
- Closing the app or laptop does not stop cloud work.[3]
- Local Mac/Windows execution is a separate capability, default ask every time.[19]
- Team admins: Bot runs as non-root; hosted MCP tokens stay on Cursor’s backend, not on the VM; static egress IPs; org admins can Kill the VM (durable storage kept).[5]
- Hardware security keys: WebAuthn in the VM browser is forwarded to the member’s desktop (Windows forwarding rolling out).[5]
Operate vs rent (house rule — on-prem vs cloud is the wrong axis): Grok’s computer is rented and operated by the vendor. You cannot SSH in as a first-class admin surface. You use it.
What Hermes has that rhymes — and what does not
❓ Does Hermes already have “a computer,” and does Nous Portal add one?
Hermes never lacked a place for commands to run. It lacked a productized, furnished, always-on office VM as the default.
Terminal backends (configuration docs): local | docker | ssh | modal | daytona | vercel_sandbox | singularity.[13]
| Backend | What persists | Who operates | Closest Grok analog |
|---|---|---|---|
| local | Your real machine | You | Grok’s optional local-computer policy — except Hermes defaults here |
| docker | One long-lived container across tool calls, /new, subagents for the life of the process (optional persist-across-processes) |
You | A sandbox VM, not a signed-in desktop |
| ssh | A remote server you own | You | Closest operate equivalent of “work continues when the laptop closes” |
| modal / daytona / vercel_sandbox | Serverless / workspace sandboxes; docs say Daytona/Modal hibernate when idle | Mixed rent | Cloud isolation, usually not a logged-in Chrome with your Gmail cookies |
| singularity | HPC container | You | Not a teammate PC |
Hermes docs: “Talk to it from Telegram while it works on a cloud VM you never SSH into yourself. It’s not tied to your laptop.”[8] That is you placing the harness on a VPS. Grok Bot is that VPS, pre-furnished, with a live desktop view.
Nous Portal does not give you Grok’s computer. It gives:
- Inference catalog (300+ models, one bill).[9]
- Tool Gateway: Firecrawl search/extract, FAL images, OpenAI TTS, Browser Use cloud Chromium, optional Modal cloud terminal sandbox.[9][25]
- Hermes Cloud (preview): one-click always-on agent in a hardened container, scales to zero when idle, billed to credits, memory lives with the agent, Telegram/Discord/Slack/Email/CLI.[11]
Those are rented tool backends and a rented harness host. They are not “one Linux desktop with your Slack cookies, /workspace, and parallel Bot screens.”
A Portal subscriber who wants Grok-like persistence today operates a VPS or SSH backend, or waits for Hermes Cloud to grow a real desktop — which it has not documented as of 2026-08-25.
Shared computer vs isolated profile
❓ Should multiple bots share logins, or should each bot be a tenant?
This is the deepest product disagreement.
Grok’s bet: handoffs are cheap when everyone already has the cookies. A sales Bot and an ops Bot can continue each other’s files. The cost is explicit: “Do not use separate Bots as a security boundary.”[19] Deleting a Bot does not wipe VM files or sessions.[20]
Hermes’ bet: a Bot is a profile directory. Credentials, memory, skills, and chat are isolated. Bot-to-bot mail is a CLI handoff (hermes -p <other> chat …), not a shared cookie jar.[21] Group rooms can even span machines (@name-device).[21]
Grok optimized coordination latency. Hermes optimized blast-radius.
Hard-to-vary test: If Grok isolated cookies per Bot, overnight CRM handoffs would need a secrets plane they currently get for free. If Hermes shared a browser profile across Bots by default, a compromised “researcher” Bot would read the “payroll” Bot’s sessions — the failure mode Grok documents in the open.
Refutability: Per-bot VMs from Grok, or a first-class shared-browser profile in Hermes, would collapse this distinction.
Reach example: This is the same design fork as “one shared corporate laptop vs one laptop per contractor.”
Computer use is not the host
❓ Is GUI clicking the same layer as “having a computer”?
No. Computer use is a tool family (pixels, accessibility tree, mouse). Host is where that tool runs.
Grok combines them: computer use on the persistent VM. Hermes can computer-use via Browser Use (Portal) or local CDP on whatever backend you set. A Hermes agent on local with a browser is powerful and stops when your laptop sleeps, unless you put the harness on SSH/Cloud.
House visual language: “where it runs” was a violet banner on Harness, not Model. This comparison says: promote that banner. The host is not a Tools doodle of a sandbox shovel. It is why Grok Bot exists.
Unresolved host facts
- Exact VM size, idle billing, and disk retention SLA: not public in the fetched docs.
- Whether Grok’s “always on” is a warm VM 24/7 or a fast resume: docs say jobs do not stall; Cloud Agents toggle is a Cursor cloud-agent launch, on by default for teams.[5]
- Hermes Cloud instance sizes and regions: FAQ exists on the marketing page; operational detail was not in the extracted FAQ body.[11]