This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Give Expo Simulators sessions descriptive names and tags, then list, filter, and stop them from EAS CLI or expo.dev.

Expo Simulators is a limited-access preview. It is not included with paid or free plans and is currently available only to select partners. Join the waitlist if you are interested in trying it.

Every Expo Simulators session belongs to an EAS project. A session can have a name, which tells people what the session is for, and tags, which group related sessions. Use names and tags to find a session later and to find sessions that are still running. Then stop the sessions that you no longer need.

Name each session

Pass --name to eas simulator:start. The name appears in eas simulator:list, in eas simulator:get, and on the Simulator sessions page on expo.dev. Without a name, each row shows a generic title and an ID, which is hard to scan.

Write the name for a person who reads the list days later:

Follow these rules:

• Use 3 to 6 words. The list shows the name on one line and cuts off a long name. The limit is 255 characters.
• Use sentence case, without a period at the end.
• Do not repeat what the list already shows, such as the platform, the date, or the person who started the session.
• Include a ticket or pull request number when there is one.

EAS CLI and the expo.dev dialog treat a name that contains only spaces as no name. The REST API and create session links reject it.

Tag related sessions

A tag is a label that groups sessions, for example, one tag for each app variant or each pull request. Repeat --tag for each tag:

A session can have up to 16 tags, and each tag can have up to 64 characters. EAS removes spaces at the start and end of each tag, stores tags in lowercase, and removes duplicates. A tag can contain a colon, such as variant:pro.

You can also add tags in the Advanced options of the Create new simulator dialog on expo.dev.

List and filter sessions

eas simulator:list shows the sessions of the current project:

You can combine these filters, and repeat each one except --name:

The list shows 10 sessions by default. Use --limit for up to 100 sessions on each page. To get the next page, pass the endCursor value from the previous JSON response to --after:

The JSON output contains a sessions array and a pageInfo object. Each session includes its ID, name, tags, type, status, platform, timestamps, and session page URL.

Find and stop sessions that are still running

A session that you started with --non-interactive runs until you stop it or until it reaches a limit. To find sessions that are queued, starting, or running, and stop one:

The queued and starting filters need EAS CLI 24.9.0 or later. Earlier versions report those sessions as new.

See sessions on expo.dev

The Simulator sessions page of a project lists its sessions:

https://expo.dev/accounts/<account>/projects/<project>/simulator-sessions

The list shows a status for each session: Starting, Live, Finished, or Failed. These labels match the new, queued, starting, in-progress, stopped, and errored status values.

Each session has its own page. The start command prints this URL, and eas simulator:get returns it:

https://expo.dev/accounts/<account>/projects/<project>/simulator-sessions/<session-id>

Delete a finished session

You can delete a session from its page on expo.dev after it finishes. Deleting a session also deletes its recordings and screenshots, and you cannot undo it. You need the Developer role or higher.

Common questions