Skills

Skill 30 of 38

Encore Login

Log the Encore CLI in to Encore Cloud, check who is logged in, sign up for an account, and log in without a person using an auth key.

2 minutes · 366 words · 7 sections

Install

$ npx skills add encoredev/skills --skill encore-login

$ npx skills add encoredev/skills

» /plugin marketplace add encoredev/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Logging in to Encore Cloud

Creating apps on Encore Cloud and deploying need a login. Running locally (encore run, encore test, encore check) doesn’t.

Instructions

1. Check who is logged in

encore auth whoami

logged in as <email>: done.
logged in as app <app-id>: logged in with an auth key. It works for that app only, and can’t create apps. If you need to create an app, go to step 2.
not logged in.: go to step 2. If no person can approve a login, such as in CI, go to step 3.

2. Log in with a person’s approval

Start encore auth login as a background command. It doesn’t exit until someone approves the login.
Its output has Your pairing code is <code> and a URL. Send both to the user right away. Ask them to open the URL on any device, check that the code matches, and approve. New users can sign up on the same page.
Wait for Successfully logged in!, then run encore auth whoami to confirm.

This works over SSH, in containers, and in cloud sandboxes too, because the user can open the URL anywhere.

3. Log in without a person: auth key

Ask the user to create an auth key in the Cloud Dashboard (App Settings > Auth Keys) and set it as the ENCORE_AUTH_KEY environment variable for the agent, for example from a secret store.
Run encore auth whoami. It should print logged in as app <app-id>. Every encore command logs in with the key automatically when nobody is logged in.

Limits of auth keys:

One app: the key can clone, link, and deploy its own app.
No new apps: encore app create and encore app init need a person’s login. For a new app, ask the user to create it in the Cloud Dashboard, then clone it with encore app clone <app-id>.
Ignored when someone is logged in: run encore auth logout first to use the key instead.
warning: ENCORE_AUTH_KEY login failed: <error>: the key is wrong or was deleted. Ask for a new one.

Log out

encore auth logout

This also stops the Encore daemon. It starts again with the next encore command.

Guidelines

Never ask the user to paste an auth key into the chat, and never pass one on the command line with encore auth login --auth-key: it ends up in shell history and process listings.
Log in before encore app create if the app should deploy to Encore Cloud. Linking an app created logged out takes extra steps (see encore-link-app).
Next: create an app (encore-create-app) or deploy one (encore-deploy).
Docs: https://encore.dev/docs/cli/cli-reference (opens in a new tab)

About this skill

Trigger

Log the Encore CLI in to Encore Cloud, check who is logged in, sign up for an account, and log in without a person using an auth key. A login is needed to create apps on Encore Cloud and to deploy them.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/encoredev/skills, branch main, last pushed 26 October 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

38 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: encore/*/SKILL.md.

Issue colours

Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “7 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

38 editorial notes across 38 of 38 skills. They are printed in the margin of each skill rather than as errors here.

Encore API — 1 note
Encore Architecture — 1 note
Encore Auth — 1 note
Encore Bucket — 1 note
Encore Cache — 1 note
Encore Code Review — 1 note
Encore Create App — 1 note
Encore Cron — 1 note
Encore Database — 1 note
Encore Deploy — 1 note

and 28 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Encore, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /encoredev/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Logging in to Encore Cloud

Creating apps on Encore Cloud and deploying need a login. Running locally (encore run, encore test, encore check) doesn’t.

encore auth whoami

logged in as <email>: done.

logged in as app <app-id>: logged in with an auth key. It works for that app only, and can’t create apps. If you need to create an app, go to step 2.

not logged in.: go to step 2. If no person can approve a login, such as in CI, go to step 3.

Start encore auth login as a background command. It doesn’t exit until someone approves the login.

Its output has Your pairing code is <code> and a URL. Send both to the user right away. Ask them to open the URL on any device, check that the code matches, and approve. New users can sign up on the same page.

Wait for Successfully logged in!, then run encore auth whoami to confirm.

This works over SSH, in containers, and in cloud sandboxes too, because the user can open the URL anywhere.

Ask the user to create an auth key in the Cloud Dashboard (App Settings > Auth Keys) and set it as the ENCORE_AUTH_KEY environment variable for the agent, for example from a secret store.

Run encore auth whoami. It should print logged in as app <app-id>. Every encore command logs in with the key automatically when nobody is logged in.

Limits of auth keys:

One app: the key can clone, link, and deploy its own app.

No new apps: encore app create and encore app init need a person’s login. For a new app, ask the user to create it in the Cloud Dashboard, then clone it with encore app clone <app-id>.

Ignored when someone is logged in: run encore auth logout first to use the key instead.

warning: ENCORE_AUTH_KEY login failed: <error>: the key is wrong or was deleted. Ask for a new one.

encore auth logout

This also stops the Encore daemon. It starts again with the next encore command.

Never ask the user to paste an auth key into the chat, and never pass one on the command line with encore auth login --auth-key: it ends up in shell history and process listings.

Log in before encore app create if the app should deploy to Encore Cloud. Linking an app created logged out takes extra steps (see encore-link-app).

Next: create an app (encore-create-app) or deploy one (encore-deploy).

Docs: https://encore.dev/docs/cli/cli-reference