Cornilius CLI — operate your analytics memory from the terminal
Command-line client

Cornilius CLI

Operate your analytics memory from the terminal.

The CLI is the human front door to Cornilius. You type a question — or a slash command — and it compiles to the same dispatch the Claude.ai MCP tools use. One vocabulary, two front doors. Run a saved playbook, recall what was analyzed last week, or ask something new, without leaving your shell.

Install

Requires Node.js 18 or newer. Run it without installing, or install it globally.

Run without installing

npx cornilius

Or install globally

npm i -g cornilius

Then run cornilius, sign in with /login, and start typing.

Command vocabulary

Natural language is the primary input — just type your analytics question and Cornilius runs the analysis. Slash commands handle control and structured operations. The grammar is modelled on Claude Code.

Cornilius CLI commands and what each one does
CommandWhat it does
just type…Ask anything — Cornilius runs the analysis
/playbooksList your saved playbooks (numbered)
/run <#|id>Run an exact playbook — no guessing
/recall [topic]What Cornilius remembers: issues, insights, history
/delete <type> <id>Delete something — two-step, asks you to confirm
/statusTenant, session, usage
/login /logoutSign in via the browser / sign out
/clearClear the screen
/helpShow the command list
/exitQuit (or Ctrl-D)

Full command reference coming soon

Sign in through the browser

The CLI signs you in the way native apps should (RFC 8252): it opens your browser to the Cornilius sign-in you already use, then hands the result back to a one-time local listener. No tokens are pasted by hand, and no new credentials are created.

  1. Run /login

    The CLI starts a one-time local listener on 127.0.0.1 and opens your browser to sign in.

  2. Sign in at cornilius.ai

    The same sign-in you already use. No new account, no separate password. PKCE and a CSRF state value protect the exchange.

  3. Return to the terminal

    The browser hands the authorization code back to the local listener, which exchanges it for a token. You are signed in.

  4. Token stored locally

    The token is written to ~/.cornilius/credentials.json with 0600 permissions. CORNILIUS_TOKEN still works as a manual override for CI.