# 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.

Cloud is in private beta. Use the Cloud address supplied with your invite;
there’s no public signup. 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

1. Create your account with an invite code, or sign in to an existing account.
2. Choose **Personal** or a team from the profile menu, then choose **New instance**
   from **Instances**. The new machine belongs to the selected profile.
3. Choose Slack or Telegram, then your AI provider. Use the suggested model
   settings or customize the supported options.
4. Review the profile, machine name, and timezone, then launch.

Setup saves your progress. Open the instance again whenever you’re ready to continue.

For shared machines, see [Personal, teams, and transfers](/docs/cloud/teams/).
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.

- **Slack:** create the app from the supplied manifest, install it to your
  workspace, and enter the requested bot and app tokens. Open the bot’s private
  conversation and send the one-time pairing command shown in Cloud.
- **Telegram:** create a bot with BotFather, enter its token, then open the
  verified bot link and tap **Start** to pair your private chat. Use a new bot
  so another service isn’t trying to receive its messages.

The first connection is personal. To add shared Slack channels later, use
[Configuration](/docs/configuration/) and [Workspaces](/docs/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.

## Sign in and say hello

For **Claude Code**, choose **Get Claude sign-in link**, then **Sign in with
Claude**. Sign in with your Claude subscription and approve access. Copy the code
Claude gives you, paste it into the Cloud form, and choose **Connect Claude**.
You can refresh Cloud and return to the same sign-in; if it expires, start again
for a fresh link. Your code is sent to your instance, where Claude Code saves
the login. It isn’t saved in your browser or Cloud account.

For **Codex**, choose **Get Codex sign-in code** and copy the one-time code.
Open **Sign in with ChatGPT**, enter the code on OpenAI’s page, and approve
access. Return to Cloud and choose **Connect Codex** to finish. If OpenAI asks,
enable device-code login in your ChatGPT security settings; workspace accounts
may require an administrator to allow it. You can refresh and resume the same
sign-in for up to fifteen minutes, or cancel and start again.

Older instances use console sign-in; expand **Sign in using the console** for
instructions. Your Cloud account and AI account are separate.

Return to setup, 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, you can open the desktop, browse the [web viewer](/docs/web/), or review
the machine details.

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, retry the current check or open the console to inspect it.
The [CLI reference](/docs/cli/) covers status and diagnostic commands. Deleting
an instance removes its files, workspaces, and saved sessions; the current Cloud
preview has no automatic recovery.

## Manual setup

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

```bash
# 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:

```bash
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](/docs/configuration/);
the rest of the Enso guides apply to your cloud computer too.