Get started with Enso Cloud

Enso Cloud gives your Enso a computer of its own. Talk to it in Slack or Telegram, and open its desktop or activity viewer from your browser when you need to check in.

Open Enso Cloud, choose Create an account, and paste the Invite code you were sent. Account creation is invite-only, and a password needs at least 10 characters. Instances are free during beta, and you bring your own AI account.

Before you begin

You’ll need an invite to create a Cloud account, a Slack workspace or Telegram account, and your own supported AI account. Cloud setup currently offers Codex and Claude Code. A Cloud account does not include access to their models.

Launch your Enso

Create your account with an invite code, or sign in to an existing account.
Choose Personal or a team from the profile menu, then choose New instance on Instances. An empty profile offers Create instance instead. The new machine belongs to the selected profile.
Choose Slack or Telegram, then your AI provider. Keep the suggested model and effort, or open Model settings to pick from the supported combinations.
Review the owning profile, instance name, and timezone, then choose Launch Enso. The timezone is prefilled from your browser and takes a name like America/Vancouver or Europe/London.

Setup runs in six steps — Chat, AI, Launch, Connect, Sign in, and Say hello — and saves your progress. Building the machine takes a few minutes, so you can close the page and open the instance again whenever you’re ready to continue.

For shared machines, see Personal, teams, and transfers. It covers creating teams, account notifications for invitations, member roles, and handing an existing instance to another team.

Connect your chat

Once the machine is ready, follow the connection steps on its setup screen.

Connect Slack: create the app, enter its two tokens, and pair your private conversation with the one-time command.
Connect Telegram: create a bot and pair your private chat through its verified Start link.

When pairing succeeds, choose Save connection to write the chat connection and your AI defaults to the machine.

The first connection is personal. To add shared Slack channels later, use Configuration and Workspaces to choose where Enso responds and give each channel its own context and instructions. Workspace boundaries organize that context; the underlying agent’s permissions control its access to tools and files.

Follow the guide for your selected provider:

Sign in with Claude Code: open its sign-in link, then paste the returned code into Cloud and choose Connect Claude.
Sign in with Codex: enter its one-time code on OpenAI’s page, then return to Cloud and choose Connect Codex.

Older instances use console sign-in. Every provider step also keeps a Sign in using the console section for recovery; it opens by default on a machine that needs it. Your Cloud account and AI account are separate.

Return to setup, choose Start Enso, and send a message in the paired conversation. Cloud checks for a successful reply before marking setup complete. Until then, the instance shows Setup in progress. A prepared machine or detected login alone doesn’t mean everything is connected.

Come back any time

Open your instance to resume unfinished setup or check its status. Once setup is complete, Open viewer shows the read-only web viewer, Open console opens the desktop, and Machine details lists the instance ID, region, machine size, timezone, and Enso version. On machines set up before the guided wizard, that desktop button reads Open desktop instead.

Closing a desktop tab leaves the computer and its apps running. Reconnecting returns to the same desktop. Chrome on that computer is also available to your agent, so the accounts you sign into there become part of what it can work with.

If setup gets stuck, use Check again at the current step. Provider sign-in offers console recovery where needed. You can choose Delete instance below unfinished setup even while the machine is provisioning. Normal management appears after the first successful reply. The CLI reference covers diagnostic commands.

Desktop and browser

Open the desktop from a completed instance. Focus the field you want on the remote screen, paste into the Paste text panel, then choose Paste to terminal or Paste to browser / app. Neither button sends Enter. Line breaks need a separate confirmation. Paste accepts ASCII text, tabs, and line breaks up to 16,000 characters; emoji and accented text are not supported by the current clipboard path. File and image transfer are not available. Apps and agents on the machine can read its clipboard, so use Clear remote clipboard after sending something sensitive; that cannot undo a paste you already made.

Disconnect closes your view and Reconnect returns to the same apps. Access expires after an hour or when you sign out of Cloud; open a fresh view from the instance page. Closing a tab does not stop the machine.

The desktop and agents share Chrome and its signed-in accounts. Opening the desktop does not pause an agent or create a private human-only session. Team members share those files and accounts too; see team access.

Machine changes and deletion

Rename, transfer, and delete live in the Instance actions menu beside the desktop button, and on the Machine details tab. Renaming changes the label in Cloud. Changing AI defaults with Edit AI settings starts verification again for the new selection; it does not replace your bot. Older machines retain the software they were created with unless explicitly updated. Use managed Enso updates for the Enso runtime; that does not replace the entire Cloud image or add new desktop and sign-in helpers.

Deleting removes the actual computer, including its files, workspaces, Enso history, provider logins, and browser sessions. There are no automatic guest backups or undelete. Save important files elsewhere first. Cloud asks you to type the instance name before Delete permanently. A failed deletion stays visible for retry.

Cloud currently has no email verification, password reset, or email delivery. Team invitations arrive in Notifications.

Manual setup

If your instance uses manual setup, use the console instead. Open the desktop’s terminal and sign in to your chosen provider:

# Codex
codex login --device-auth

# Claude Code
claude auth login

Run only the command for the provider you use. If Codex device sign-in isn’t available for your account, run codex login and finish in the remote browser.

Then run these commands one at a time:

enso setup
enso-cloud-start
enso doctor

Follow the setup prompts to connect your chat, start Enso’s background service, and resolve any failed checks. Send a message in Slack or Telegram to verify the reply. For configuration details, use Configuration; the rest of the Enso guides apply to your cloud computer too.