Authentication

Use the authentication commands before running LibOps API workflows:

sitectl libops login
sitectl libops whoami
sitectl libops logout

login opens the same browser login flow used by the dashboard, including Login with Google. The CLI listens on a temporary localhost callback URL, stores OAuth credentials in ~/.sitectl/oauth.json, and can create a saved API key for sustained access.

sitectl libops login --api-url https://api.libops.io

whoami and profile setup

whoami reports the active account, token/API-key state, GitHub username, and LibOps SSH key status:

sitectl libops whoami

Set account profile fields from the CLI:

sitectl libops account update --github-username octocat
sitectl libops account update --name "Ada Lovelace"

For checkout and SSH workflows, set your GitHub username and add the same public SSH key to both GitHub and LibOps.

API keys

Use API keys for non-interactive or long-lived access:

sitectl libops create apikey --name workstation --save
sitectl libops create apikey --name ci --scopes organization:read,project:write
sitectl libops list apikeys
sitectl libops delete apikey "$API_KEY_ID" --yes

The LibOps plugin checks for a saved API key before falling back to OAuth credentials.

SSH keys

sitectl libops create ssh-key --name laptop --public-key-file ~/.ssh/id_ed25519.pub
sitectl libops list ssh-keys
sitectl libops delete ssh-key "$KEY_ID" --yes

LibOps plugin

Resources

Task Agent

Runtime workflows

Access controls

Domains

Authentication

whoami and profile setup

API keys

SSH keys

​whoami and profile setup

​API keys

​SSH keys

whoami and profile setup

API keys

SSH keys