CLI · InstallAuthenticate

Authenticate

Login via device flow and contexts (SaaS + on-premise).

Login

eqs login uses the Device Authorization Flow (OAuth 2.0, RFC 8628). It opens the browser with a code for you to approve:

bash
eqs login
text
→ Open https://app.equantic.space/device and enter the code:

    ABCD-1234

Waiting for approval… ✓ Authenticated as ana@equantic.tech

For an on-premise installation, point to your API:

bash
eqs login --api https://api.suaempresa.com

Contexts

Like kubectl, eqs stores named contexts (~/.eqs/config.json), each with { apiUrl, token, workspaceId, spaceId }. A single CLI drives SaaS and any on-premise installation:

bash
eqs ctx list            # list contexts
eqs ctx use producao    # switch context
eqs ctx add ...         # add a new one
The token is stored in the OS keychain when available, otherwise in ~/.eqs/config.json (permission 0600). eqs logout revokes the token.
Previous
Install eqs