Commands
embr auth
Last updated October 23, 2026
embr auth login [--token <token>] [--index <index>]
embr auth logout [--index <index>]
embr auth whoami [--index <index>]
embr auth token [--index <index>]
Manages the GitHub login that embr publish,
embr yank and embr deprecate use. The commands follow pesde's
auth commands.
Subcommands#
loginsigns in with the GitHub device flow: it opens github.com/login/device and shows a code. The flow requests no OAuth scopes.--token <token>stores a GitHub token that you already have instead. Ember asks GitHub for the token's user first, so a bad token fails here and not at publish time.logoutremoves the stored login. With no login stored, it says so and succeeds.whoamiprints the GitHub user of the stored login.tokenprints the stored token, for a script or a CI secret.
With no login stored, whoami and token fail and tell you to run
embr auth login.
One login#
Ember keeps one GitHub login, in ~/.ember/credentials.toml (owner-only
on unix). The registry maps that login to the scopes you own.
Without --index, the commands use that login, whatever the
default index is. --index (-i) takes ember, a key
under [indices], or a URL, and checks that the index takes a login at
all. An index with no login, such as a wally index, fails with
Index ... does not accept publishes.
You do not have to log in first. embr publish starts the device flow
when no login is stored, and signs in again when the registry refuses a
stored token.
See also#
- Publishing for how the registry uses the login.
- Files & locations for where the token lives.