Skip to main content

​
Synopsis

​
Description

The commands that do not run tasks: credentials and docs. For the CLI version, run pome --version. Include it in any bug report.

​
pome login

Sign in through the browser and store a team API key. On macOS the key goes to the Keychain; elsewhere it goes to ~/.pome/credentials.json. Plus the global flags — --api-url, --artifacts-dir, and -V, --version.

​
pome logout

Remove locally stored credentials: the Keychain entry, ~/.pome/credentials.json, or both. Takes no flags of its own beyond the global flags, which are inert here. Signing out locally does not revoke the key on the server. Revoke it in app.pome.sh if it may have leaked.

​
Where credentials come from

Hosted commands resolve credentials in this order, and stop at the first hit:
  1. POME_API_KEY
  2. The macOS Keychain entry, security find-generic-password -s sh.pome.cli
  3. ~/.pome/credentials.json, written by pome login
With none of the three set, hosted commands fail immediately rather than running unauthenticated.

​
pome docs

Go from the terminal to a docs page without searching for it. With a topic, it prints that topic’s docs.pome.sh URL. With no topic, it opens an interactive picker.

​
Examples

Sign in against a control plane of your own:
Mint a key you can recognise later in the dashboard:
Clear the local credentials:
Open a docs topic, or print its URL for a script:

​
Exit status

See the canonical table.

​
See also

  • pome doctor: checks that your agent and twin are wired correctly.
  • pome init: the next step after signing in.
  • CLI reference: the same credential order, alongside the exit codes.