NotHoly CLI & SDK — NotHoly Docs

Versioned downloads for durable conversations, approvals and selected local context.

Install the CLI

Version 0.1.0 requires Node.js 24 or later. Install the versioned package from NotHoly, then check the executable. This download is not an npm-registry publication. Verify downloaded files against the SHA-256 manifest before installation.

Shell

npm install -g https://notholy.com/downloads/notholy-cli-0.1.0.tgz
notholy --version
notholy --help

Commands and profiles

auth login reads a key from stdin; auth status and config never print it. history lists conversations, resume follows an existing run, and mode selects a profile default. Use --profile NAME for isolated local preferences. A selected file requires --file PATH and --allow-file; Reverse uses --binary-file and Pentest uses --engagement. No command discovers or uploads a repository automatically.

Credentials and funding

Use a scoped customer key and the public HTTPS endpoint. Subscription-funded CLI work requires chat:write in addition to relevant run/session scopes. Chat, CLI and API share the published credit unit. Funding and scoped access remain enforced by the server. Registration and package installation grant no inference funds. Doctor never prints the secret.

Local permissions

Selected local files are bounded to the chosen workspace. Reviewed patches require a separate local confirmation tied to the exact before/after hashes; concurrent edits invalidate approval. A server tool approval does not authorize a local file edit or arbitrary shell command.

Install the first-party SDK

The JavaScript SDK 0.1.0 provides durable runs, sessions, approvals and artifact methods. It requires Node.js 24 or later. Native OpenAI and Anthropic protocol clients remain separate integrations documented in the API reference.

Download SDK 0.1.0

Shell

npm install https://notholy.com/downloads/notholy-sdk-0.1.0.tgz

Test and live environments

A local or isolated test fixture is not live model or payment proof. The public HTTPS service enforces its current account, model and funding rules. Install and help commands do not invoke inference; sending a run may consume usage.