login
Log in to Clonit Cloud interactively.
clonit login [flags]Arguments & Flags
Section titled “Arguments & Flags”| Flag | Type | Default | Description |
|---|---|---|---|
--auth-url |
string | discovered from cloud | Override the auth service URL |
--client-id |
string | discovered from cloud | Override the OAuth client_id |
--no-browser |
bool | false |
Do not open the verification URL in a browser |
--scope |
string | "" |
Optional OAuth scope to request |
--help, -h |
bool | false |
Show help for the login command |
This command takes no positional arguments.
Global Flags
Section titled “Global Flags”| Flag | Type | Default | Description |
|---|---|---|---|
--config |
string | ~/.config/clonit/config.yaml |
Path to the config file |
--debug |
bool | false |
Enable debug logging |
--quiet |
bool | false |
Suppress non-essential output |
--width |
int | 0 |
Table output width (0 = auto-detect terminal width) |
Description
Section titled “Description”clonit login signs you in to Clonit Cloud through your browser using an OAuth
2.0 Device Authorization Grant (RFC 8628). Clonit prints a short code and a URL,
you approve the login in your browser, and clonit stores the resulting session in
its config directory. No API key or password is typed into the terminal.
Only cloud.url is required. The auth service and client_id are discovered
automatically from the cloud’s GET /api/v1/auth/config endpoint. Use
--auth-url / --client-id to pin them instead of discovering them (for
example, against an air-gapped or self-hosted auth service).
The session (access and refresh tokens) is stored in
~/.config/clonit/credentials.json (mode 0600), separate from config.yaml,
and is refreshed automatically.
Interactive login is for humans. CI/CD and other headless automation should keep
using a Clonit Cloud API key (cloud.api_key) instead.
Examples
Section titled “Examples”Log in interactively. Clonit prints a code and URL, opens your browser, and waits for approval:
clonit loginPrint the verification URL without opening a browser (useful over SSH or in a headless shell):
clonit login --no-browserPin a self-hosted auth service instead of discovering it from the cloud:
clonit login --auth-url https://auth.example.com --client-id clonit-cliA typical interactive login lifecycle:
clonit login # print a code + URL, open the browser, wait for approvalclonit whoami # show the current login (and validate the session)clonit logout # clear the stored sessionSee Also
Section titled “See Also”- logout – Log out of Clonit Cloud and clear the stored session
- whoami – Show the current Clonit Cloud login
- Cloud Storage guide – Set up and use Clonit Cloud