Cue by Manus

An agent has its own identity, within your permissions

Manus presents each Cue agent as having its own phone number, email address, wallet, and computer. The official site says an agent can make or take calls, send messages and email, make payments with permissions you control, and keep working in a dedicated environment. The diagram shows the described relationship; it is not a Cue interface screenshot or evidence that every feature works for every account.

• Start with a narrow task and inspect the exact phone, mail, connector, and computer permissions the app requests.
• For a payment task, set a budget and review the approval step, merchant, amount, and failure or refund path in the live account.
• A dedicated agent identity does not by itself establish local phone-number support, payment eligibility, or a particular data-retention policy.

What Cue shows for calls, coordination, and routines

Cue's official demonstration shows agent identity and phone workflow screens. Its site describes agents answering forwarded calls, summarizing them, using email and connected services, working together in a group chat, and turning connected tasks into routines. A restaurant QR example describes creating an agent for a local service. These are demonstrations and examples from the publisher, not independent completion tests.

• Watch the official Cue showcase from the source list to inspect the visible phone and agent workflow; the film has audio and no verified caption track for inline playback here.
• Choose one reversible test such as asking an agent to summarize a forwarded call or draft an email, then verify the actual result and permission record.
• Treat the many travel, healthcare, booking, and payment prompts on Cue's site as possible task ideas, not proof that every integration or transaction is live.

Can you use Cue now?

Cue's current official Android listing, updated October 10, requires an invitation code and describes Plus access after entry. The official homepage is readable again. The September 29 disabled web/desktop observation is historical, not the current universal access state. Check the active app, account and platform; an Android store listing does not prove iOS approval, a working macOS download or worldwide GA.

• An invite code can run out or apply only to an eligible sign-up path; the announcement is not an access guarantee.
• The visible mobile QR does not by itself verify a working app listing, region, device support, or account entitlement.
• No lasting free plan, post-preview price, or Manus subscription inclusion is established by the launch.

When to choose Cue instead of Manus

Use Manus 2.0 when the deliverable is a project you want to build, edit, automate, or run in a Manus workspace. Try Cue when the task depends on an agent's separate communication or payment identity and ongoing personal coordination, provided the relevant feature is actually available to your account. The products share a launch and related infrastructure, but Cue is a separate app, not a Manus 2.0 subscription tier or API model.

• Manus 2.0

  Compare the project workspace with Cue's separate personal-agent app.

• For a creative deliverable, inspect Manus Studio outputs and editable files.
• For a Cue task, inspect the sent message or call summary, connected service, approvals, spend, and human handoff.
• Do not infer a one-to-one transfer of projects, credits, subscriptions, or data between the two apps without a documented account flow.

Useful first jobs

• Handle and summarize an eligible forwarded call or message.
• Coordinate a bounded booking or admin task through approved email and tools.
• Organize several agents around a shared goal in a group chat.
• Run a repeatable personal routine after checking permissions and approvals.