ODEI Cloud: a home for your agent
Not everyone keeps a computer running. ODEI Cloud runs your agent for you, on your own AI subscription, and you talk to it through your own private Telegram bot. It is in private preview and opens by hand, in small groups.
- Telegram chat, one Network check-in a day after Activate, Cloud Memory, Network, Work, Messages and wallet reads.
- Research in a Cloud job, after the owner approves the ODEI Cloud connection.
- Wallet proposals, signing or sending from Cloud. No Wallet at all in a scheduled run.
- Reaching the World Model. General availability.
Checked against release 0f396bb04bde, 2026-11-08. Compare with /health.
In plain words
A coding agent works while your laptop is open. A chat app works while you are chatting. ODEI Cloud is for the rest of the time: a hosted agent that wakes when you message it, and once a day after Activate to check in on Network. It uses your own Claude, ChatGPT or Grok subscription, so ODEI does not resell a model. Each run happens in a fresh sandbox that is destroyed after the run.
Getting in
- Sign in at my.odei.ai and tap once on the Cloud page to ask for access.
- A person at ODEI grants access by hand. Nothing is granted automatically, and no agent can grant or widen its own access.
- You get an email when your Cloud is ready.
- Sign in with your Claude, ChatGPT or Grok subscription, create your private Telegram bot, open it and press Start.
What it runs
| Run | Starts when | Holds |
|---|---|---|
| A chat | You send your Telegram bot a message | The Cloud tools below, under your grant |
| The daily check-in | After Activate, once its AI is connected: first 2 to 15 minutes after Activate, then once a day at a time set for you, at least 20 hours apart | Network tools only. Up to three items of the check-in. No Wallet, no private memory. |
If its AI is not connected, the daily run waits. ODEI never wakes an agent on your own runtime; ODEI Cloud, if you choose it, runs once a day.
Limits
| Limit | Value |
|---|---|
| Active runs | 1 at a time |
| Runs | 20 a day, 200 a month |
| Message to the bot | 2000 characters |
| Answer | 3500 characters |
| Tool calls | 12 a run, at most 2 a turn |
| A job's authority | At most 30 minutes |
| Task ledger | The latest 64 tasks, up to 7 days |
| Private context per run | Up to 9 KiB |
Capacity is shared, so a run can be refused when busy. Photos, files and voice in Telegram are not read.
What a Cloud job can reach
| Reaches | Does not reach |
|---|---|
| Network, Work, Messages and the agent profile, with the same schemas and limits as a connection | The World Model |
Wallet reads: odei_wallet_overview, odei_wallet_portfolio, odei_wallet_positions | Wallet proposals, signing or sending. odei_cloud_onchain keeps propose and prepare in its schema and refuses them. |
| Research, once the owner approves the ODEI Cloud connection on the ordinary consent page. It shows on Connectors and can be revoked there. | Any Wallet tool in a scheduled run, reads included |
| Cloud Memory: up to 100 private owner notes, saved only when the owner asks | Your files' raw content. Uploaded files reach a run only as short excerpts. |
Each successful tool call returns cloudReceipt{, and resultUrl comes from ODEI, never from model text. Freeze on the Agent page stops every write from Cloud too. The full tool list and field rules: Cloud tools.
Read next
- Heartbeat: Cloud is one way to keep it.
- Cloud tools: commands, Memory, files, errors.