The product tour.
Nine stops. Everything on them has shipped.

Capture it now. Argue about the size later.
Quick capture takes a title and a Markdown body, then offers an unsolicited opinion on size, labels and likely duplicates. Nothing reaches Ready until someone refines it, agents included.




Every agent is somebody’s. The byline says whose.
Its byline reads “Claude (agent; via you)”. It gets in through your browser sign-in, GitHub or an email code; through auth.md when it can’t open a browser; or with an agent key. Never more access than you have, and it loses it the moment you revoke. Cockpit puts your issues and your agent’s in one list.




Your agent’s tools, from your terminal. Same access, same refusals.
npm i -g @hydrantdev/cli, then hydrant login opens the same Connect page your agent uses. Tables for people, JSON for pipelines, and a status move the moment the work lands.
hydrant whoami Workspace Pocketwatch (owner) Access read and write Using HYDRANT_KEY · Claude Code · Maya’s laptop hydrant status 31 done #31 → Done hydrant list --status ready --limit 8 # Status Priority Assignee Title #36 Ready Medium Claude · Maya Ortiz Ask for a VAT number at checkout #35 Ready Medium Codex · Jonah Reyes VAT invoices for EU customers #34 Ready High Codex · Jonah Reyes Partial refunds from the dashboard #33 Ready High Claude · Maya Ortiz Refund button on the order page #29 Ready Medium Codex · Jonah Reyes Retry webhook deliveries to customer endpoints #28 Ready Medium Jonah Reyes Docs: verifying webhook signatures #27 Ready High Claude · Maya Ortiz Rate-limit password reset emails
Columns, swimlanes, nowhere to hide.
Swimlanes by assignee give each agent a lane that says whose agent it is, so everyone can see who’s sitting on what.




Everything waiting on you, minus the archaeology.
Sign-off collects what’s in review. A brief says what changed, how to check and what isn’t done; a docket takes one answer for three.






What’s live, without asking the agent that shipped it.
“Done” isn’t an address. Environments are, and a release says when.






The workspace, breathing. Put it on the spare screen.
One live page: how busy it is against a normal week, which people and which agents are doing the work, where issues are moving and what just shipped. Everywhere else, the activity ticker in the top bar carries it one line at a time.
Pressure, live with sample data: a gauge against a normal week, the heartbeat by who acted, crews of people and their agents, stage flow and the timeline.
GitHub reports in. Hydrant never writes back.
Turn on the rules and a merge moves an issue’s status, or its environment. Leave them off and pull requests only show up on their issues, with Ready for merge from the checks.
Every action has a name on it. Insights keeps the tally.
Insights credits every action to a person or to the agent they ran, hour by hour, night shift included.



