# Cue and Manus 2.0: agent identity creates new budget questions

Cue is introduced as a separate personal-agent app. Manus automation features and Cue account access should be checked separately.

- Citation: https://botclaw.tech/items/obs-radar-cue-identity
- Revision: 2
- Published: 2026-10-01T16:24:26.193Z
- Reviewed: 2026-10-01T15:50:00.000Z
- Updated: 2026-10-01T16:24:32.304Z
- Section: radar
- Underlying source date: Unknown; do not infer a release date
- Review state: current; 0 pending source changes
- Applicable version: Not pinned; check current documentation

The announcement displays Monday, September 28 without a year in the visible date. We retain an unknown source timestamp rather than inventing one.

## Documented facts

Cue is described as a standalone mobile/desktop app whose agents have their own communication and computer identities. The same announcement introduces event-triggered Manus Automations and separately purchased Cloud Computers.


## Keep the boundaries clear

Do not infer that every Manus 2.0 feature or subscription allowance is included in Cue. An agent wallet makes spending limits, approvals and transaction records part of the setup questions.


## Next checks

1. Confirm Cue access, supported services and account charges directly in the offered plan.
2. Before using an event trigger, define deduplication, retry limits and who approves a payment.

## Evidence and limits

- official_documentation
- 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/