@hone-ai/cli

Hone AI runs an 18-stage AI SDLC pipeline over your repository. You describe a story; the pipeline grooms it, plans the implementation against your real code, writes failing tests, builds, reviews for logic and security, and hands you a pull request to review like any other.

The orchestration, prompts and skills run on Hone's server. This CLI is the client.

Install

npm install -g @hone-ai/cli
hone init --token <YOUR_TOKEN>

A token is issued when your organization is provisioned. Without one the CLI installs fine but every server-backed command will refuse.

The three commands that matter

hone setup       # detect your stack, write .github/.pipeline-config.yml, install agents + skills
hone derive      # generate domain skills from YOUR codebase (the part that makes plans specific)
hone run-story   # run a story through the pipeline

hone setup inspects the repository rather than guessing: it finds where your source actually lives and writes that into codebase.source_dirs, which is what the pipeline uses to ground every agent in your real file layout. Check it afterwards with:

hone doctor --check source-dirs
hone detect-layout

If source_dirs is wrong the pipeline is grounded on a partial map, so this is worth thirty seconds.

Running a story

hone run-story 412                  # a GitHub issue number
hone run-story HC-101 --include-paths src/api/orders.js

The run pauses at review gates. Approve or inspect:

hone run-story <run-id> --status
hone show step <run-id> step_1      # what the agent actually produced
hone run-story <run-id> --approve step_1

Editor mode

By default the pipeline's generation steps run on Hone's server. In editor mode the build step runs in your own editor's AI on your own plan, and Hone orchestrates and verifies around it. Set execution.mode: editor in .github/.pipeline-config.yml, then:

hone step-instruction <run-id>      # what your editor should execute
hone submit-step <run-id>           # hand the result back for gating

Hone does not select or provision your editor's plan, and you remain responsible for complying with your agreement with that provider.

Useful extras

hone status              # pipeline state for a story
hone workflows           # in-flight runs
hone usage               # your org's token usage against its budget
hone doctor              # repo health checks
hone billing             # subscription status

hone --help lists the full command surface.

Requirements

Node.js 20 or newer, and a git repository.

Support

hone doctor first — it catches most configuration problems and tells you the fix. Beyond that, contact the person who issued your token.

License

UNLICENSED. Proprietary; use is governed by your agreement with Hone AI.