#Authentication

The Flowingto CLI uses a secure device authorization flow to authenticate users.

#flowingto login

Run the login command to authenticate:

flowingto login

What happens under the hood:

1. The CLI requests a device code from the Flowingto server.
2. A browser window opens automatically with the verification URL.
3. You approve the device in the browser.
4. The CLI polls the server for an access token and stores it locally.

#flowingto logout

Clear all stored credentials:

flowingto logout

This removes the credentials file from your local machine.

#flowingto whoami

Display the currently logged-in user:

flowingto whoami

This shows your email, user ID, token expiration time, and the server you are connected to.

#Credential Storage

Your credentials are stored at:

~/.flowingto/credentials.json

The file is created with restricted permissions (0o600) and contains:

• email
• token
• server
• userId
• expiresAt

Expired tokens are treated as invalid, so you will need to log in again when the token expires.

#Custom Server

For local development or self-hosted instances, use the --server global option:

flowingto --server http://localhost:3000 workspace list