> For the complete documentation index, see [llms.txt](https://mercure-technologies.gitbook.io/expo-open-ota/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mercure-technologies.gitbook.io/expo-open-ota/eoas/overview.md).

# Overview

EOAS is an npm CLI for managing application updates.

Use it to:

* Deploy and republish updates.
* Roll back an update.
* Initialize a project and generate certificates.
* Audit an existing configuration.

EOAS works in a developer's local environment and in CI pipelines.

### Authentication

{% tabs %}
{% tab title="Control plane mode" icon="plane-up" %}
In [Control plane mode](/expo-open-ota/controle-plane-mode/overview.md), EOAS authenticates with `EOO_TOKEN`.

Generate `EOO_TOKEN` from the dashboard. It is an application-scoped API key.

The database stores only the token hash. The original token cannot be retrieved after creation.

Use a separate key for each CI environment or workflow. Keep every key secret.

{% endtab %}

{% tab title="Stateless mode" icon="bolt-lightning" %}
In [Stateless mode](/expo-open-ota/stateless-mode/overview.md), EOAS uses Expo authentication for update operations.

Set `EXPO_TOKEN` in the terminal to provide an Expo access token explicitly. This is recommended for CI.

When `EXPO_TOKEN` is absent, EOAS reuses the active EAS session. Run `eas login` first.

Use a dedicated Expo token for automated workflows. Keep it in your CI secret store.

{% endtab %}
{% endtabs %}

### Pin the EOAS version in CI

{% hint style="warning" %}
Never run unversioned `npx eoas` in CI. Always use an explicit EOAS version.
{% endhint %}

An unpinned command can fetch a newer CLI release unexpectedly. This can introduce breaking changes into a pipeline.

Use the EOAS version that exactly matches the server version:

`npx eoas@<server-version> <command>`

EOAS releases stay synchronized with the server version during release publishing. Update the CLI version whenever you upgrade the server.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mercure-technologies.gitbook.io/expo-open-ota/eoas/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.