@solomei-ai/auth

The public bootstrap for Callimacus. One callimacus login configures everything a developer needs to build on Callimacus: the private SDK download (~/.npmrc) and an API key — with zero prior setup.

This package is intentionally small and public so a new client can run it before they have any credentials. The full operator/tenant-config CLI is the private @solomei-ai/callimacus-cli, installable only after login configures the registry.

npx @solomei-ai/auth login

Prefer npx. Both this package and @solomei-ai/callimacus-cli install a binary named callimacus, so a global install of this one can win the $PATH race and shadow the full tool. Since 1.2.0 the full CLI mounts these same commands, so once it is installed you do not need this package on $PATH at all — callimacus login works from either.

Requires Node.js ≥ 24 (the active LTS). Supported Node lines are the current LTS and newer. The hard technical floor is 22.12.0 — commander v15 is ESM-only and is loaded via require(esm), which Node only supports from 22.12.0 on — but Node 22 is in maintenance and is not a supported target.

First run

npx @solomei-ai/auth login          # device-code → writes ~/.npmrc + the API profile
npm i -g @solomei-ai/callimacus-cli # now installs (private, via the configured registry)
callimacus login                    # the full tool carries these commands too, from 1.2.0
callimacus configure …              # …alongside everything else

login uses a device-code flow: it prints a URL + short code, opens your browser (falling back to "paste this URL" on headless boxes), you approve in the dashboard, and it writes the credentials. The registry token goes to user-level ~/.npmrc; the API token is stored as a profile in ~/.callimacus/config.json — the same file @solomei-ai/callimacus-cli reads, so this one login configures that CLI too.

Commands

| Command | What it does | |---|---| | login | Authorize this machine (device-code; or no-op materialize from CALLIMACUS_NPM_TOKEN in CI). | | scaffold | Scaffold the current project: .npmrc scope map, .env API key, .gitignore. Named init before 1.2.0 — renamed because the full CLI has an unrelated init, and Commander shadows a duplicate name silently. | | whoami | Show the active profile + project, and whether ~/.npmrc is configured. | | use <project> | Switch the active project profile. | | logout [project] | Strip the registry lines from ~/.npmrc and remove one profile, or all of them. | | setup-ci [--print] | Configure the registry from CALLIMACUS_NPM_TOKEN (writes ~/.npmrc, or prints with --print). |

CI

A developer with several projects has one registry token (machine-level) and a per-project API key. In CI, skip the browser:

env:
  CALLIMACUS_NPM_TOKEN: ${{ secrets.CALLIMACUS_NPM_TOKEN }}   # the registry token
steps:
  - run: npx @solomei-ai/auth setup-ci   # writes ~/.npmrc headlessly
  - run: npm ci

Configuration

| Env var | Default | Purpose | |---|---|---| | CALLIMACUS_API_URL | https://api.callimacus.ai | API host (device-flow endpoints). Override for dev. | | CALLIMACUS_REGISTRY_URL | https://npm.callimacus.ai | Private registry the .npmrc points at. | | CALLIMACUS_NPM_TOKEN | — | Registry token for non-interactive login/setup-ci. The former name CALLIMACUS_TOKEN is still accepted (with a deprecation warning). |

Notes

• Config interop: writes ~/.callimacus/config.json in the exact schema @solomei-ai/callimacus-cli (its lib/config.ts) reads, so the two share one profile.
• SDK env var names: scaffold writes CALLIMACUS_CLIENT_ID / CALLIMACUS_CLIENT_SECRET to .env — the current names the @solomei-ai/callimacus-sdk env wrapper reads (CALLIMACUS_PUBLIC_KEY/PRIVATE_KEY still work but the SDK logs a deprecation warning).
• No native deps: pure Node + commander (≥ Node 24 LTS), so npm i -g / npx work on Windows, Linux, macOS, and WSL. 0600/0700 file modes are enforced on Unix; on Windows they no-op and the files rely on the user-scoped profile dir (same posture as aws/gcloud/gh).