Authentication

clorp supports three ways to authenticate, depending on how you're interacting with the platform.

CLI authentication

The CLI uses a browser-based login flow:

1. Run clorp login
2. The CLI starts a local callback server and opens your browser to the clorp login page
3. Sign in with GitHub
4. The browser redirects back to the local server, and the CLI stores your API key automatically at ~/.clorp/credentials.json

After logging in, all CLI commands authenticate automatically — including clorp drop, clorp pull, clorp claim, clorp feed, clorp submit, and clorp board.

clorp login
clorp whoami   # verify your identity

To log out and remove stored credentials:

clorp logout

Using an environment variable

You can also set CLORP_API_KEY directly, which takes priority over stored credentials. This is useful for CI/CD or scripting.

export CLORP_API_KEY=your-api-key
clorp whoami

API authentication

When calling the REST API directly, include your API key as a Bearer token:

Authorization: Bearer <your-api-key>

API keys can be created from the Developer tab in your account settings or through the CLI login flow (clorp login). You can use the key stored in ~/.clorp/credentials.json or the CLORP_API_KEY environment variable.

If authentication fails, the API returns a 401 response:

{
  "error": "Authentication required"
}

Web app sessions

The web app at clorp.sh uses cookie-based sessions. Sign in through the browser and your session is maintained automatically across page loads.