EASwitchMultiple Expo accounts, one machine

Keep typing eas. Save each Expo account once, link each project, and every eas command uses the right account, without logging in and out.

Get started

See an example

Command reference

GitHub

Your normal login stays put

eas build, eas whoami and expo start keep working exactly as before. Only easw commands switch accounts.

Per-project accounts

easw link pins a project to an account. Every easw command in it, from easw whoami to easw submit, then runs as that account.

Any EAS command

easw build, easw update, easw submit, easw env:list… every EAS CLI command runs as the selected account.

Tokens in your keychain

Access tokens live in macOS Keychain, Windows Credential Manager or Linux Secret Service. Never in config files.

Log in or paste a token

Add accounts with Expo's own login (browser, password or SSO) or an access token. EAS CLI comes bundled.

Keep typing eas

Run easw hook once, and plain eas uses the linked account inside linked projects. Works in zsh, bash, fish, PowerShell and cmd.

Quick start

Set up once:

bash

npm install -g easwitch       # install (EAS CLI is included)

easw add personal             # save each account once: log in, or paste an access token
easw add work
easw hook                     # plain `eas` now follows project links (then open a new terminal)

cd ~/code/acme-app
easw link work                # this project belongs to "work"

Then keep using eas as usual:

bash

eas whoami                    # in acme-app: the "work" user
eas build --platform ios      # built as "work"
cd ~ && eas whoami            # everywhere else: your normal login

Prefer not to change eas? Skip easw hook and type easw instead (easw whoami, easw build…). To add the hook to your shell config yourself, use easw shell-init.

EASwitch demo: linking a project, turning on the shell hook, then using plain eas as the linked account

Working at a company? An Acme example

Jane uses her personal Expo login for her own apps, a separate work user for Acme's app, and a client's token for freelance work. She saves each account once, links each project, and from then on every easw command in a project uses the right account. Her normal Expo login stays available elsewhere.

Follow the Acme walkthrough for the commands, the shell hook, common situations, and the difference between an Expo user and an Expo organization.