Blog · Analysis
Cue Agents vs DeepSeek Harness: personal identity agents meet an open harness
September 29, 2026 · dshbase · X pulse
On September 28, 2026, Manus shipped Manus 2.0 and, beside it, a standalone app called Cue. The account @CueAgents introduced itself with a short line — personal agents, on Cue — and pointed at cue.im. The paragraph that actually describes the product is section 3 of the Manus 2.0 post, “Cue: A new app from Manus.” This note is the day-after reading for people who already run DeepSeek Harness.
Cue and DSH are not 1:1 substitutes. Cue is a closed consumer app for personal life operations. Each agent is issued an email, a phone number, a wallet, and a computer, and several of those agents can share a group chat. DSH is an MIT-licensed harness for people who build and customize agent runtimes: plugins, sandboxes, sessions, a Web UI you start yourself. Launch-day threads will rhyme them. This note keeps the categories apart.
What actually shipped
Cue is Manus’s personal multi-agent app, built on the same infrastructure as Manus, and offered on phone, desktop, and web. @CueAgents described early access as free and limited, and named Android, Mac, and Windows as the clients you can open now. iOS has been submitted for App Store review, which is “coming soon,” not a build you can install from the store today. Early access is free with an invite code. A starter code, MEETCUE, has been mentioned in public as limited and first-come. Manus has not published a price for after early access. A missing price is a missing price. This note will not invent one.
The feature that defines the product is the identity stack, which gets its own note in email, phone, wallet, computer. Official copy says each agent can message, pay inside a budget you set, run tasks on its own machine, take calls, and leave the summary back in Cue. Phone numbers, Manus says, exist for Manus and Cue agents in select countries for now, and some of those lines are voice-only. There is no country list in this article, because publishing one would mean guessing.
The multi-agent surface is a group chat with a shared goal. Agents hand work to each other. You set the direction and you keep the final call. The everyday example in the Manus post is the kind of chore a coding harness does not have a noun for: scan a restaurant QR code, and the agent orders or holds a place in line. That sentence is the category label. Cue is trying to act in the world on your behalf. DSH is trying to be the runtime under tools you write.
Manus 2.0 also named Cascade, an in-house harness, plus Cloud Computer, Automations, and Manus Studio. That is context for the stack Cue sits on. Cascade’s percentages stay in the Cascade note, labeled as Manus’s own one-config self-test.
@ManusAI framed the launch as introducing personal agents on Cue. Community summaries arrived within hours. @bb833dong and @ZachFeng compressed the feature list for Chinese readers. @FanShifu mused about use cases. Those posts are useful as a temperature reading. They are not a specification, and a tidy thread is not evidence that Cue and dsh web are two skins on one idea.
At a glance
| Cue Agents | DeepSeek Harness | |
|---|---|---|
| License | Closed consumer app | MIT, open source |
| Audience | Someone who wants agents to handle life ops | Someone building or customizing an agent runtime |
| Identity stack | Email, phone, wallet, and computer per agent | Sandbox, tools, and plugins. No carrier number or wallet as a product primitive |
| Multi-agent UX | Group chat. Agents hand off. You keep the final call | Teams, shared boards, sessions — a builder surface |
| Extensibility | You use the app. The agent loop is not yours to fork | Everything is a plugin, on Cordis |
| Hosting | Manus-hosted: web, desktop, mobile | You run it. Web UI via npx @deepseek-ai/dsh web, or headless |
| Pricing model | Early access free with invite. Post-EA price not published. Starter code MEETCUE is limited | The harness is open source. You pay the model provider you point it at |
| Maturity | Day-one product. iOS in App Store review. Phone numbers in select countries | Developer preview. APIs can break |
Read each row as a category difference. A cell that says DSH does not ship a phone number is a description of the job, not a bug filed against the harness. A cell that says Cue does not ship a forkable loop is a description of a consumer app, not a missing plugin.
Where they rhyme
Three ideas show up on both sides. They are why a comparison is worth writing, and why it has to stay inside those ideas.
Handoff. Cue’s group chat is a room where several agents share a goal and pass work. DSH’s team tab and shared task boards are a room where several sessions pass work. The glass-room Agent Team article already argued that a visible handoff is the point. The board pulse added the invoice: an unlimited handoff is a meeting that bills by the token. Cue makes the same bet inside a chat transcript. The practical map — approval, hop limits, when chat is enough — is in the group-chat guide.
Each worker has a machine. Cue says each agent has a computer and can run tasks on it. DSH says a session can have a sandbox, tools, and a workspace. “Has a computer” is the rhyme. What that computer is allowed to touch — a restaurant line, a repository, a payment — is the divergence, and it is the whole subject of the identity note.
You remain the director. Cue’s copy keeps the final call with the person. DSH’s glass room keeps a project manager in the loop on purpose. Both products, on the evidence we have, still expect a human to set direction. A demo that implies a staff you cannot interrupt is ahead of either write-up.
Where they diverge
Open plugins versus a closed app. DSH’s sentence is “everything is a plugin.” Models, tools, sandboxes, session storage, and UI are swappable modules on the Cordis kernel. You can read the loop. The repo is deepseek-ai/deepseek-harness. The docs live at deepseek.com/harness. Cue does not offer that sentence. You receive an app. You do not receive a plugin store aimed at harness authors, and you do not receive a fork of the agent loop. That split is the same one this site already drew in DeepSeek Harness vs Claude Code, pointed this time at a life-ops product instead of a coding client.
Life operations versus a coding harness. Cue’s examples are messages, calls, payments inside a budget you set, and a restaurant QR. DSH’s examples are files, tools, traces, and plugins. A DSH reader who wants an agent to text a restaurant is looking at the wrong install command. A Cue reader who wants to swap the sandbox or pin a model is looking at the wrong app. The chooser at the end of this batch is there so those two readers stop sharing one screenshot.
Bring your own model versus an opaque harness. DSH is explicit about the model. You point the runtime at a provider, the mode presets are yours to pick, and the preview nature of the APIs is part of the contract. Cue runs on Manus infrastructure. The new in-house harness under that stack is Cascade, and Manus has not published Cascade as open source. You can audit a DSH session. You cannot audit Cascade from the outside. Any efficiency percentage attached to Cascade stays a vendor self-test until someone who does not work at Manus can reproduce the configuration.
Who should open cue.im tonight
Open cue.im if the thing you wanted this week was a personal agent with a real contact point: an inbox, a number, a budgeted wallet, a machine that is not your repository. The invite gate is part of the product. MEETCUE is a public starter code, and it is limited. If the code is exhausted, waiting is the state of early access. If you need iOS today, the App Store review is still in front of you. If you need a phone number, the official line is select countries, some of them voice-only, and a reply on X is not a coverage map.
Stay on npx @deepseek-ai/dsh web if you are building. DSH is the lane where the loop, the tools, the sandbox, and the session are yours to replace. It is still a developer preview. Interfaces move. That is the cost of a harness you can read, and it is a different cost from a day-one consumer app. Use Cue when life-ops identity is the job. Use DSH when the job is the harness. The other four notes in this batch take one slice of that sentence each: the identity stack, the group chat, Cascade, and the launch-day chooser.
Sources
The Manus blog is the official description. Posts from @CueAgents and @ManusAI are launch copy from the maker. The other X links are community signal, useful for what people heard, not for filling gaps in the spec.
- Manus — Introducing Manus 2.0, section “3. Cue: A new app from Manus.”
- cue.im — Cue product site.
- DeepSeek Harness docs and deepseek-ai/deepseek-harness.
- @CueAgents — hello world.
- @CueAgents — free, limited early access; Android, Mac, and Windows.
- @ManusAI — introducing personal agents on Cue.
- @bb833dong — community summary.
- @ZachFeng — Chinese-language community summary.
- @FanShifu — use-case musing.