Developers
CentraKit CLI authentication, API base resolution, token options, and release assets.
The centrakit CLI lives in apps/cli and talks to the public API. It is the supported command-line entry point for local automation, headless scripts, and MCP-adjacent workflows.
The CLI resolves its API base URL in this order:
--base-url.CENTRAKIT_API_URL.https://api.localhost/api.https://api.centrakit.com/api.The /api path is part of the base URL because API route handlers live under that prefix.
Interactive local use should start with:
centrakit loginThe login flow uses browser-based PKCE against Supabase OAuth and stores refreshable credentials locally.
Headless use should provide a bearer token:
CENTRAKIT_TOKEN=<access-token> centrakit organizations listor:
centrakit --token <access-token> organizations listCLI releases are prepared through Release Please. After the release PR is merged, the CLI release workflow packages a tarball and attaches it to the GitHub release.
See CI And Release for the release workflow details.