Cue: a practical decision dossier

Before you start

• Check current account access, plan and task requirements.

When to consider it

Consider it for delegated service tasks only after checking access, payment controls and what each identity can do.

Important boundary

A Manus subscription or automation announcement does not establish Cue entitlement. Phone, wallet and local-service availability need direct confirmation.

Questions before committing

1. Who approves spending, and where is the per-agent limit enforced?
2. Can one agent’s resources and conversation be separated from the team?

A useful acceptance task

Give the candidate one read-only task with fixed input, a clear expected output and an explicit stop condition. Save the input, returned evidence, elapsed time and any human intervention. Repeat after a new session; assess observed behavior, not a polished demo.

Evidence and limits

Official documentation checked

• Source-backed facts plus BotClaw editorial interpretation. No product account, inference or agent performance test was run.

Sources

• https://manus.im/zh-cn/blog/introducing-manus-2-0
• https://cue.im/

Continue the decision

• Cue and Manus 2.0: agent identity creates new budget questions
• What should an agent ask before doing?
• What does an always-on agent actually cost?