dshbase

Blog · Analysis

Email, phone, wallet, computer: Cue’s identity stack vs DSH sandboxes

September 29, 2026 · dshbase · X pulse

Cue’s launch sentence is an identity sentence. Manus says each agent gets its own email, its own phone number, its own wallet, and its own computer. That quartet is the product. DeepSeek Harness does not ship a quartet like it, and a fair reading starts by admitting the absence is structural. DSH gives you a sandbox, a tool surface, and a plugin kernel. “Having a computer” is a phrase both sides can say. The computers are not the same object. This note defines the primitives, then says what each side actually hands you. The flagship comparison is Cue Agents vs DeepSeek Harness. Cue and DSH are not 1:1 substitutes, and the identity stack is the clearest place to see why.

Four primitives, as Manus described them

The official description is in the Cue section of the Manus 2.0 post. Read as a stack, the four pieces do different jobs.

  • Email is a contact point the agent can send and receive on, separate from your personal inbox. The agent can message as itself.
  • Phone is a number the agent can use for calls and texts. Manus has said Manus and Cue agents can have phone numbers, in select countries for now, and that some of those lines are voice-only. The country set is not published here, because it is not ours to invent.
  • Wallet is a way to pay, inside a budget you set. The control Manus is willing to name in public is that budget. A post-early-access price for Cue itself has not been published, and a wallet budget is not that price.
  • Computer is a machine the agent runs tasks on. Official examples include everyday services such as scanning a restaurant QR so the agent can order or hold a place in line, and taking a call, then leaving the summary back in Cue.

Put together, the stack is a claim that the agent can show up in systems that already exist: inboxes, phone networks, payment rails, and a computer that is not the chat window. @ManusAI and @CueAgents launched that claim on September 28, 2026, with the app at cue.im. Early access is free with an invite. The public starter code MEETCUE is limited. iOS is in App Store review. None of those availability facts change what the four primitives are. They change when you can touch them.

What “a computer” means on the Cue side

On the Cue side, the computer is part of a hosted personal agent. You do not provision it as a plugin. Manus runs the app — web, desktop, and mobile, with Android, Mac, and Windows called out for the free limited window — and the agent’s machine is one of the things the app includes. The interesting property is reach. A computer that can hold a place in a restaurant line is a computer pointed at the outside world, paired with an identity that the outside world can call back.

The controls Cue is willing to describe are human ones. You set the budget the wallet may spend. You set direction. You keep the final call, including when several agents share a group chat. Those are product claims from the Manus post, not an independent security audit. They matter because a phone number and a wallet are higher-blast-radius primitives than a sandbox pointed at a git checkout. A budget and a final human call are the brakes Manus has put in the launch copy. Whether those brakes hold under abuse is a question the launch post does not answer with a report, and this note will not pretend it did.

The community reaction understood the blast radius immediately, which is why the jokes arrived with the launch. @ExiledonMoon posted a spam joke about agents that can be reached. Treat it as humor, not as a vulnerability write-up. It is still the right instinct: a number that can receive is a number that can be abused, and a wallet that can pay is a wallet that can be talked into paying. The official mitigation on the page is the budget you set and the final call you keep. Hold the product to that sentence.

What “a computer” means in DSH

In DeepSeek Harness, the computer is a sandbox you configure. The harness is MIT-licensed, “everything is a plugin” on Cordis, and still a developer preview whose APIs can break. You start it yourself — npx @deepseek-ai/dsh web for the Web UI, or a headless run — and you point it at a model with your own API key. A session gets tools, a workspace, and a permission boundary. The sandbox guide on this site is the practical version: approvals, presets, and the habit of not letting a tool run because the demo looked calm.

That sandbox can feel like “the agent has a computer,” and for coding work it is one. It can read a tree, run commands inside the boundary you allowed, and leave a trace you can replay. It does not, out of the box, possess a carrier phone number, a payment wallet, or an email identity on a public network. If you want mail, you bring an email plugin or an MCP tool and you bring the credentials. If you want a model other than the default path, you bring the key. The equivalent of Cue’s stack, inside DSH, is a composition: sandbox, plus tools, plus whatever plugins you trust with your own accounts. The composition is the product. The accounts are yours before they are the agent’s.

MCP fits in the same sentence. A server you attach can expose a capability the core harness does not ship — a browser, a ticket queue, a mailbox API. The MCP note is how that attachment works. Attaching a mailbox API is not the same as Manus issuing the agent an address. You remain the account holder, the key holder, and the person who uninstalls the plugin. That is the builder contract. It is slower than opening cue.im, and it is the contract DSH readers already accepted when they chose a harness over an app.

What each side does not ship

CueDeepSeek Harness
Contact pointEmail and a phone number, select countries, some voice-onlyYou integrate mail or messaging yourself, if you want it
MoneyA wallet, spent inside a budget you setNo wallet primitive. Spend is your model bill and anything a plugin is allowed to call
MachineA computer included with the hosted agentA sandbox and a workspace you run
LoopClosed. Not a forkable agent loopReadable, replaceable, plugin-shaped
Extension store for harness authorsNot the productThe product. Plugins are how capabilities arrive

The bottom two rows are what Cue does not ship, and they are easy to skip because the top rows are flashier. Cue is not offering harness authors a place to publish a sandbox implementation. DSH is not offering consumers a phone number. Wanting both in one install is a reasonable wish. It is not what either launch described.

One unofficial thread needs a label before it hardens into a fact. A Grok post circulated chatter about US numbers for these agents. That post is not Manus. It is not a country list. Manus’s own wording is “select countries,” with some lines voice-only. If your decision depends on a specific country, the source is Manus, not a reply.

Which computer you actually wanted

Choose Cue’s computer when the task leaves the repository. Ordering from a QR code, taking a call, paying inside a cap you set, and writing the summary back into the app are life-ops jobs. The identity stack is what makes those jobs legible to restaurants, carriers, and inboxes. You accept a closed app, an invite gate, and a phone story that is still geographically partial.

Choose a DSH sandbox when the task is the runtime. You want to see the loop, swap a tool, pin your own key, and keep the workspace on a machine you administer. You accept that a phone number and a wallet are projects you would have to build, with credentials you already hold, and that the preview can break an API you depended on last week. The group-chat guide is the next slice: once an agent has a machine, how several of them hand work across, and which control surface you are actually holding.

Sources

Identity claims below come from the Manus blog. X posts are community signal except where they are the maker’s own launch posts. The Grok link is unofficial and is cited only so it does not get promoted into a coverage map.

All articles →