@skopiklabs/cli

First-party command-line interface for Skopik agents, durable sessions, and Remotes.

Run or install

Run the latest release without a permanent installation:

npx skopik --help
npx skopik run --agent release-helper --prompt "Draft the release notes"

The scoped package works directly too:

npx @skopiklabs/cli@latest --help

Install the skopik binary permanently:

npm install --global @skopiklabs/cli
skopik --help
skopik update

Node.js 20 or newer is required.

skopik update upgrades the global @skopiklabs/cli installation to the latest npm release. It does not require a Skopik API token.

Auth and config

For interactive use, sign in through the Skopik console:

skopik login
skopik auth status
skopik whoami
skopik logout

skopik login starts a callback on a random 127.0.0.1 port and opens the console approval page. Use skopik login --no-open when browser auto-open is unavailable on the same machine. For a remote SSH host, forward the printed callback port or use an API key. The flow uses PKCE; access tokens refresh automatically. Refresh credentials live in the OS credential store when available. If it is unavailable, the CLI warns and uses ~/.config/skopik/auth.json with mode 0600.

API keys remain the right choice for CI, servers, and other unattended use:

export SKOPIK_API_KEY=sk_live_...
export SKOPIK_BASE_URL=https://api.skopik.com/api/v1

skopik config set token sk_live_...
skopik config set base-url https://api-staging.skopik.com/api/v1
skopik config set org org_123
skopik config get

Credential precedence is --token, SKOPIK_API_KEY, the token in ~/.config/skopik/config.json, then the browser login. Global flags override environment variables and the config file:

skopik --base-url http://localhost:3010/api/v1 --token sk_dev_... agents list

Use --json for machine-readable output. sessions stream --json emits one JSON frame per line so callers can process the stream incrementally.

Run an agent

run defaults to an agent_done session, waits locally for it to settle, and prints the final assistant response:

skopik run --agent release-helper --prompt "Draft the release notes"
skopik run --agent agent_123 --prompt-file ./prompt.md --json

If the local wait times out, the durable session keeps running and the error includes its session id so you can reconnect.

Durable sessions

skopik sessions open --agent release-helper --prompt "Help coordinate launch"
skopik sessions list --status waiting --limit 20
skopik sessions get sess_123
skopik sessions send sess_123 --text "Also include migration notes"
skopik sessions messages sess_123
skopik sessions stream sess_123
skopik sessions children sess_123
skopik sessions approve sess_123 op_123 --reason "Expected deployment command"
skopik sessions cancel sess_123

Session opens support model and reasoning overrides, Remote or sandbox reach, completion policy, limits, output schemas, living keys, metadata, continuation, and idempotency keys. Run skopik sessions --help for the complete flag list.

Agents and brain files

skopik agents list --limit 20
skopik agents create --name "Release Helper" --model openai/gpt-5.5 --can-write
skopik agents brain write agent_123 AGENTS.md --file ./AGENTS.md

Remote mode

skopik remote up --label "Build Mac" --root ~/skopik-workspaces

Development

npm run build --workspace=@skopiklabs/cli
npm run test --workspace=@skopiklabs/cli
npm run dev --workspace=@skopiklabs/cli -- --help

The main commands are login, logout, auth, config, whoami, update, agents, run, sessions, and remote.