Skip to main content
The hookie CLI manages your Hookie account and its projects: everything the console and the MCP tools can do, as commands. Use it from a terminal, a script, a CI job, or give it to an AI agent. Every command goes through your account in Hookie; nothing is received on, or forwarded to, the machine it runs on.
  • --json on every command and a real exit code when something fails, so a script or an agent can act on the result.
  • A hookie.yml you can review in a pull request: written from a project with hookie export, applied with hookie apply, and checked for drift with hookie diff.

Install

Node 20 or newer. The CLI is a single file with no dependencies, served by Hookie itself:
Run the same command again to update.

Sign in

That opens Hookie in your browser, waits for you to approve the connection, and stores the resulting token in ~/.hookie/credentials.json with mode 0600. Nothing is pasted anywhere: it is the standard OAuth 2.1 authorization-code flow with PKCE, the same one connected agents use, so hookie login and an agent you connect share one credential store.
A new connection starts read-only. Widen it in Settings → Connected agents, where you can also revoke it — immediately, and per connection. A CLI connection appears in that list exactly like an agent, because it is one.
Three more commands round that out: hookie logout keeps the registered OAuth client so the next hookie login reuses it instead of adding another row to your agent list. Revoke it on the server too if you mean to cut it off there.

Which Hookie, which project

Commands talk to https://app.hookie.ai. --project takes a slug or an ID; with neither, commands use your workspace’s Default project.
Until you run hookie login, a command stops before sending anything and says Not connected to https://app.hookie.ai. Run: hookie login. To use a token instead of a stored connection (in CI, for example), see Configuration.

What it will and will not print

stdout is data; stderr is progress, warnings and prompts. So hookie endpoints list --json | jq works, and so does redirecting stdout while still watching what happens.
An endpoint’s public URL is a credential — the slug in it is what authenticates the request. It is printed by default anyway, because it is the point of hookie endpoints create, and the CLI says so on stderr when it does. Use --redact when the output is going into a ticket, a log or a chat.
A destructive command asks first. On a non-interactive stdin it refuses rather than assuming yes — a CI job that means it passes --yes, and one that did not mean to gets an error instead of a deletion.

Where to go next

Operations

Send a test event, find what failed, and redeliver it.

Command reference

Every command, generated from the same catalog the CLI builds itself from.

Configuration

hookie.yml, environment variables and exit codes.

Connected agents

The same OAuth connection, from your coding agent instead.