> For the complete documentation index, see [llms.txt](https://docs.tessl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessl.io/administrators/eu-region.md).

# Using the EU region

Set up the Tessl CLI for an organization using the EU region.

Use this guide if your organization was provisioned on [eu.tessl.io](https://eu.tessl.io). The web app is at `https://eu.tessl.io`, and the CLI uses the API at `https://api.eu.tessl.io`.

## Set the EU environment

Make sure `TESSL_ENV=app-eu` is set in your shell environment before you run any `tessl` command. The CLI reads it each time it starts. Unless `TESSL_API_BASE_URL` or `TESSL_WEB_BASE_URL` is also set, this selects the EU API and web app.

Add the setting to your shell profile so new terminals inherit it. Use the profile for your shell:

```shell-session
$ echo 'export TESSL_ENV=app-eu' >> ~/.zshrc
$ source ~/.zshrc
```

```shell-session
$ echo 'export TESSL_ENV=app-eu' >> ~/.bashrc
$ source ~/.bashrc
```

On Windows PowerShell, persist the setting for your user, then open a new PowerShell window:

```powershell
[Environment]::SetEnvironmentVariable('TESSL_ENV', 'app-eu', 'User')
```

If you prefer not to change your profile, set the variable inline on each command instead:

```shell-session
$ TESSL_ENV=app-eu tessl login --device
```

## Log in

Use device login for the EU region:

```shell-session
$ tessl login --device
```

The CLI shows a code and the shared device login URL, `https://auth.tessl.io/device`. Open the URL, sign in, and enter the code.

Confirm that the CLI is using the EU environment:

```shell-session
$ tessl whoami
```

The output includes `Environment: app-eu`. It appears whether or not you are logged in, so you can also use this to check the setting before you log in.

## CLI files and global content

Unless `TESSL_GLOBAL_DIR` is set, the EU CLI stores its data in `~/.tessl_app-eu`. This is separate from the US CLI directory, `~/.tessl`, so credentials, globally installed tiles, and globally installed plugins do not transfer between regions. Install any global tiles and plugins again after you log in to the EU region.

If your environment sets `TESSL_API_BASE_URL`, `TESSL_WEB_BASE_URL`, or `TESSL_GLOBAL_DIR`, review or remove those overrides before you use the EU region. They take precedence over the regional defaults and can select a different endpoint or storage directory.

## CI, MCP servers, and agents

Set `TESSL_ENV=app-eu` in the environment that starts the CLI. This applies to CI jobs, MCP servers, and agent integrations that run `tessl`.

For example, set the variable in a CI job environment:

```yaml
env:
  TESSL_ENV: app-eu
```

Recipe sandboxes launched from the EU instance receive this setting automatically. You do not need to set it in a skill, recipe, or schedule.

## Availability

The public registry and public publishing are not available in the EU region.

The CLI will select your region at login in a future update. Until then, keep `TESSL_ENV=app-eu` set in the environment the CLI runs in.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tessl.io/administrators/eu-region.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.