Surfaces · CLI

The same actions,
straight from the shell.

Pipe-friendly commands for humans and agents running in shell mode. One binary, one token, one project graph — same backend as MCP, same IDs, same audit trail.

~/work/hydrant
$ hydrant issue create "PAT handoff" --milestone account-handoff
HYD-88 created · branch feat/pat-handoff
$ hydrant decision add "PATs are one-time reveal" --link HYD-88
DEC-24 linked to HYD-88
$ hydrant deps set HYD-88 --blocks HYD-89
dependency graph updated
$
Install

One binary. Same auth token.

Install the CLI, sign in with a personal access token, and pin the active space. The same PAT works across MCP, REST, and the CLI — revoke once and every surface stops talking.

Homebrew

Three lines to a working CLI

Same script for fresh laptops and rebuilt containers.

brew install hydrant/tap/hydrant
hydrant auth login --pat hyd_sk_…
hydrant use <space>
Command groups

Every Hydrant primitive, mapped to a verb.

The CLI mirrors the MCP tool catalog one-for-one — issues, decisions, planning, notes, files, and context assembly. Subcommands stay grouped so muscle memory transfers between agents and shells.

Issues

4 cmds
hydrant issue createhydrant issue listhydrant issue updatehydrant deps set

Decisions

3 cmds
hydrant decision addhydrant decision listhydrant decision link

Planning

3 cmds
hydrant cycle currenthydrant cycle listhydrant milestone create

Notes

3 cmds
hydrant note createhydrant note listhydrant folder create

Files

3 cmds
hydrant file savehydrant file listhydrant file url

Context

3 cmds
hydrant searchhydrant bundlehydrant preflight
Example session

From idea to preflight in five lines.

Spin up an issue, capture the constraint as a decision, lock the dependency, bundle the context, and run preflight — all without leaving the shell. Same identifiers your agent will see when it picks the work up.

~/work/hydrant
$ hydrant issue create "Audit logout on stale tokens" --priority high
HYD-491 created · assigned to you
$ hydrant decision add "Revoke on logout, not on token expiry" --link HYD-491
DEC-77 linked to HYD-491
$ hydrant deps set HYD-491 --blocks HYD-492
HYD-491 now blocks HYD-492
$ hydrant bundle HYD-491 --files
6 decisions · 4 files · 2 linked issues · ready for paste
$ hydrant preflight HYD-491
3/3 readiness checks · HYD-492 unblocked
$
Auth · identity

Mint a token, bind it to the shell, revoke it when it's done.

Personal access tokens are the only credential the CLI needs. Generate one in settings, paste it into hydrant auth login, and rotate or revoke without touching the rest of your stack.

Get a personal access token
Closed beta · invite only ]

Stop typing what your
agent already knows.