# Hydrant

> Hydrant is the tracker for when your agents do most of the work. Agents take the work over MCP; Sign-off is where you review what they finished.

Operated by Background Craft LLC. You bring an email address or a GitHub account to sign in with, and your own MCP agent client (Claude Code, Claude, Codex or any client that speaks Streamable HTTP). Hydrant doesn’t run agents or sell a model. Start on Free. Upgrade to Solo Pro or Team from Settings → Billing whenever you outgrow it. Free is $0. Solo Pro is USD $6 per month or $60 per year per account. Team is USD $12 per human per month or $120 per human per year. Prices exclude applicable tax. Environments come with Solo Pro or the 14-day trial: up to 10 per workspace, with approvers, promotions and named releases. Free has none. Private workspace content requires authentication and is not part of these public materials.

## Product

- [Overview](/index.md): What Hydrant does today (including the Hydrant CLI, Pressure and the activity ticker, email sign-in and auth.md registration for agents), who it is for and what it costs.
- [Product](/product.md): Capture, agents, the CLI, the Board, Sign-off, releases, Pressure, GitHub and Insights. All shipped.
- [Manifesto](/manifesto.md): How Team Hydrant builds with AI agents, and the rules that keep them honest. Hydrant enforces the ones a server can and hands agents the rest in writing.
- [Pricing](/pricing.md): Free for one human. Solo Pro is $6 a month for up to three. Team is $12 a human a month. Agents never take a seat. Unlimited issues on every plan.
- [FAQ](/faq.md): Straight answers about Hydrant: Sign-off, the Board, environments, which agents connect and where it’s listed, pricing, exports and your data.
- [Privacy](/privacy.md): What Hydrant stores, who processes it, how long it is kept, and how to see, fix, export or delete your data.
- [Data handling](/data-handling.md): Who processes Hydrant data, where it is stored, how long it is kept, and how requests and incidents are handled.
- [Terms](/terms.md): Terms of service for Hydrant, an issue tracker for builders and their agents: accounts, acceptable use, billing, refunds and liability.
- [Security](/security.md): How to report a security vulnerability in Hydrant, what is in scope, and what happens after you report.
- [Agent Work Record](/agent-work-record.md): An open spec for agent work: who was allowed, what shows it was done, who said it was good. One JSON file any tool can write.

## Help

- [Hydrant Help](/help.md): How to use Hydrant, plan with it, run the workspace and connect your own agents. Every page here, one click away. No chatbot.

### Start here

- [Get started](/help/using/getting-started.md): Sign in with GitHub or an email code, create a workspace and file your first issue in Hydrant, in about five minutes.
- [Find your way around](/help/using/find-your-way.md): The sidebar, the top bar, Quick capture, the Find it command palette, keyboard shortcuts and how Hydrant's addresses work.
- [Views, filters and saved views](/help/using/views-and-settings.md): Pick a built-in view, narrow it with filters, shape it with Display, and save the result for yourself or the whole workspace.
- [Board](/help/using/board.md): Issues as columns of cards. Columns, swimlanes and groups, moving cards, ordering cards that tie, phones, and a note for anyone coming from Linear.
- [Notifications](/help/using/notifications.md): What makes Hydrant notify you, where notifications show up, and how to read, snooze, delete and tune them.

### Issues

- [Capture and edit issues](/help/using/issues.md): Create issues fast, write in Markdown, attach images, discuss in threads, read the history and recover things from the trash.
- [Status, Refined and Blocked](/help/using/status-refined-blocked.md): Three separate answers about an issue - where it is, whether it's understood, and whether something is in its way.
- [Sign-off](/help/using/sign-off.md): One page for work waiting on your word, from review-stage issues, approvals and dockets to new specs and answers to your notes.
- [Labels, sizes and priority](/help/using/labels-sizes-priority.md): Tag issues with labels, set priority from Low to Urgent, and size work with T-shirt or Fibonacci ranks, plus who manages each.
- [Relationships](/help/using/relationships.md): Connect issues as blockers, sub-issues or related work, read the Blocked and Blocks chips, and open the dependency graph.
- [Snooze](/help/using/snooze.md): Hide an issue until a date and time you choose, in a timezone you choose, and know exactly what happens when it wakes.

### Planning

- [Projects and milestones](/help/planning/projects.md): Create a project, give it an outcome and milestones, move issues into it, and close it with evidence instead of vibes.
- [Roadmap and delivery targets](/help/planning/roadmap.md): Give projects, milestones and issues a year, quarter or month, read the Roadmap, and review what a period actually delivered.
- [Cycles and the planning calendar](/help/planning/cycles.md): Turn on repeating work cycles, assign issues, let unfinished work roll forward on its own, and read the burnup without squinting.
- [Insights](/help/planning/insights.md): What the Insights page counts - work in flight, in versus out, what needs a decision, who holds what, velocity - and how to read it.
- [Pressure](/help/planning/pressure.md): What the live Pressure page shows (the gauge, heartbeat, crews, stage flow and the timeline) and how the table and TV mode work.

### Workspace

- [Members and invitations](/help/workspace/members.md): Invite people by email, pick Owner, Admin or Member, change roles, remove people, leave, transfer ownership, and see exactly who can do what.
- [Settings map](/help/workspace/settings.md): Every Hydrant settings page, grouped Personal, Workspace, Work and Agents - what each one is for, who can open it, and where the destructive buttons live.
- [GitHub pull requests](/help/workspace/github.md): Connect repositories so pull requests show up on the issues they mention, and optionally move issue status or environment. Hydrant never writes to GitHub.
- [Plans and billing](/help/workspace/plans-and-billing.md): Free, Solo Pro and Team with exact limits and prices, Team seats, the 14-day trial, upgrading, switching, canceling, and what happens at a limit.
- [Account, export and deletion](/help/workspace/account-and-data.md): Your account and preferences, exporting a workspace, deleting a workspace or your account, and how long Trash keeps things. Exact consequences included.

### Agents

- [Connect your agent](/help/agents/connect.md): Point Claude Code, Claude, Codex or another MCP client at Hydrant, approve it in the browser and confirm it can read.
- [Let an agent register itself](/help/agents/auth-md.md): An agent that can't run a browser sign-in can register through auth.md with your email. You approve it with a six-digit code.
- [What you're approving](/help/agents/consent-and-access.md): How the browser consent screen works, what read only and read and write cover, and what an agent can never do.
- [Prove the connection works](/help/agents/first-read.md): Make the first verified read, find it under Access and give your agent a sensible first task before it writes anything.
- [Copy a prompt for your agent](/help/agents/copy-prompt.md): Copy a one-click prompt for an issue's next step (refine, prep and go, resume or ship), or one orchestrate prompt for a selection. The templates are yours to edit.
- [The workflow pack](/help/agents/workflow-pack.md): Free skills that teach Claude Code and Codex to capture, refine, prep, go, triage review and ship in your repository, installed by a setup skill that asks first.
- [Playbook and guides](/help/agents/playbook.md): Write guides once, attach them to issues or make them workspace defaults, review changes, and see exactly what guidance an agent received.
- [Named agents and ownership](/help/agents/named-agents.md): Create named agents to assign work to, record who owns or maintains each one, and show a named agent's face on a connection's comments and changes.
- [Agent keys](/help/agents/agent-keys.md): Create a workspace-scoped key, hand it to a client safely and revoke it when you're done.
- [Use the Hydrant CLI](/help/agents/cli.md): Run Hydrant's agent tools from a terminal or a CI job. Sign in with your browser, or use an agent key. Tables for people, JSON for scripts.
- [Reconnect, expire, revoke](/help/agents/reconnect-and-revoke.md): How long an agent's sign-in lasts, how to reconnect it, and how to cut off a connection or key immediately.
- [Writes that don't bite](/help/agents/safe-writes.md): The rules Hydrant enforces on agent writes - request IDs, versions, receipts and separate operations - and how a well-behaved agent follows them.
- [When an agent gets stuck](/help/agents/troubleshooting.md): What each agent error means, from 401 to 503, and what to do about stale versions, uncertain retries and rate limits.

## Log

- [Log](/log.md): What shipped, how it was built, and what we think about it. Written by people. Occasionally with agents, and we say so.
- [I liked Superpowers. My docs folder didn't.](/log/i-liked-superpowers.md): Jesse Vincent's Superpowers skills made my agent brainstorm, plan and test first. They also filed a dated plan in my repository every time I used them, and none of those plans knew when it was done.
- [Hydrant and Jira](/log/hydrant-and-jira.md): Jira suits organizations that need breadth and control; Hydrant suits a small team running an explicit human-and-agent delivery loop.
- [Hydrant and monday.com](/log/hydrant-and-monday.md): monday work management lets teams configure an operations system. Hydrant supplies a narrower issue system with fewer knobs.
- [Hydrant and Asana](/log/hydrant-and-asana.md): Asana connects tasks to portfolios and company goals. Hydrant keeps a compact delivery loop for a much smaller team.
- [Hydrant and ClickUp](/log/hydrant-and-clickup.md): ClickUp consolidates work across a configurable hierarchy. Hydrant keeps one software-delivery loop deliberately bounded.
- [Our decisions file is a history, not a spec](/log/our-decisions-file-is-a-history-not-a-spec.md): We split current instructions from decision history so agents can start quickly without losing the reasons, reversals and rejected work behind them.
- [Hydrant and Basecamp](/log/hydrant-and-basecamp.md): Basecamp gives a project one room for work and conversation. Hydrant keeps a narrower contract around each ticket.
- [The test was faster than React](/log/the-test-was-faster-than-react.md): A browser test saw the new URL, raced ahead of the screen, and blamed the picker it closed along the way.
- [Hydrant and Trello](/log/hydrant-and-trello.md): Trello makes a board easy to shape and automate. Hydrant fixes more of the software-delivery meaning in advance.
- [Merged isn't done](/log/merged-isnt-done.md): One settings change passed review and merged cleanly, then stayed unfinished until the released product proved the same thing.
- [Hydrant and Obsidian](/log/hydrant-and-obsidian.md): Obsidian is a local knowledge environment; Hydrant is a shared issue tracker for accountable delivery by people and agents.
- [What our agents cost in CI time](/log/agents-made-our-ci-bill-a-product-decision.md): Agent throughput turned repeated test runs into a design problem for our delivery process, measured in runner time rather than guesses about money.
- [Look us up in Claude](/log/look-us-up-in-claude.md): Hydrant is listed in Claude's connector directory as a Community connector. Add it, approve one workspace, choose read only or read and write, and start asking.
- [Hydrant and Notion](/log/hydrant-and-notion.md): Notion keeps projects beside the knowledge that explains them. Hydrant gives software tickets a narrower shared meaning.
- [Hydrant and GitHub Issues](/log/hydrant-and-github-issues.md): GitHub Issues keeps tasks beside code and pull requests; Hydrant gives a small human-and-agent team a separate delivery workspace.
- [Hydrant and Linear](/log/hydrant-and-linear.md): Both trackers work with agents. The useful choice is about the size and shape of the work around them.
- [Hydrant and Markdown files](/log/hydrant-and-markdown.md): Markdown task files are cheap, portable and reviewable; Hydrant supplies shared state and coordination that a repository must otherwise maintain.
- [Steal our workflow](/log/steal-our-workflow.md): We wrote down the steps our agents follow before they build and ship. You can use the same workflow and change the parts that don't fit.
- [We forgot to launch](/log/we-forgot-to-launch.md): Hydrant went live without an announcement. Seventeen days in, here is what shipped, what is on the bench and what is on ice.
- [What agents can't touch](/log/what-agents-cant-touch.md): A missing production secret stopped an agent's deployment. The useful part was what it did next: leave the release unfinished and ask.
- [Why I built another issue tracker](/log/built-by-the-agents-it-tracks.md): I still love Linear. Years of using and studying trackers helped me work out what I wanted for my own projects and the agents building them.
- [Your work and your agents](/log/your-work-and-your-agents.md): Cockpit now keeps your tickets and your personally owned agents together, while Watchtower shows the team moving around them.

## Service availability

- [Service status](https://status.hydrant.dev): Public website/application reachability, reported interruptions and maintenance. This does not guarantee every feature is available.