Agent-native project context

The project system
your agent already speaks.

Hydrant lives where work happens — inside the conversation you're already having with your agent. File issues from a chat. Ship them from the same chat. The same actions are available in your shell.

Get a personal access tokenView MCP setup
$brew install hydrant/tap/hydrant
pi — ~/work/hydrant
pi·project context: hydrant connected
>
Works where agents work
Claude Code
Cursor
Codex
Codex
OpenCode
Windsurf
and others...
The shape of the problem

Project trackers were built for humans clicking buttons.

Your agent has codebase context. It knows the file the bug lives in, why the regression happened, what the fix probably touches. But until now, the only way to capture that into a ticket was for you to leave the conversation, open a tracker, and re-type what your agent already knew.

Hydrant exposes the same project actions over MCP and CLI — so "create the issue" and "ship the issue" stay inside the loop you and your agent are already in.

Operator choice

MCP or CLI.
Same project context underneath.

Some operators want agents to call tools directly. Others prefer commands they can inspect, paste, script, and run themselves. Hydrant keeps both surfaces on the same object model, permissions, identifiers, and audit trail.

MCPfor tool-calling agents

Let the agent operate Hydrant directly.

Expose issues, decisions, milestones, notes, files, dependencies, and execution briefs as structured tools inside any MCP-capable agent.

Tool groupscore surface + more
Issues
get_issuecreate_issueset_dependencies
Decisions
create_decisionlist_decisionsupdate_decision
Planning
create_milestonelist_cyclesget_cycle_issues
Notes
create_notelist_noteslist_folders
Files
save_filelist_filesget_file_url
Context
searchpreview_bundleand_more
mcp configHTTP + PAT
{
  "mcpServers": {
    "hydrant": {
      "type": "http",
      "url": "https://hydrant.dev/mcp",
      "headers": { "Authorization": "Bearer hyd_sk_…" }
    }
  }
}
CLIfor shell-first operators

Run the same actions from the terminal.

Pipe-friendly commands for humans and agents running in shell mode. Same backend, same IDs, same dependency graph — no context fork.

~/work/hydrant
$ hydrant create issue "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
$ hydrant bundle HYD-88 --files
6 decisions · 4 files · 2 linked issues
$ hydrant preflight HYD-88
✓ met 3 criteria · HYD-89 now unblocked
$
Installsame auth token
brew install hydrant/tap/hydrant
hydrant auth login --pat hyd_sk_…
hydrant use hydrant
And also

When MCP and CLI aren't where the work is.

Hydrant's core is the object model: issues, decisions, notes, dependencies, files, milestones, and audit. These secondary surfaces exist for moments where the right interface is a webhook, service, CI runner, or borrowed shell.

REST

For automation and CI.

Plain JSON over HTTPS for webhooks, CI runners, and services that should not install a binary or host an MCP client.

POST/v1/issues
{
  "title": "Audit logout on stale tokens",
  "priority": "high",
  "blocks": ["HYD-489"],
  "labels": ["auth", "security"]
}
SSHSoon

For zero-install moments.

A temporary terminal view for borrowed laptops, fresh containers, and shells where installing a binary is the wrong move.

$ ssh hydrant.dev
Hydrant TUI · preview
And a web view

For reading the room, not pushing the buttons.

The Feed is the cockpit: what changed, who changed it, which issues heated up, and what your agents just did. It is built for review and orientation when the terminal scroll is no longer enough.

  • Grouped by issue so agent activity is readable, not noisy.
  • Insight ribbon pulls out blockers, bursts of work, and review-ready threads.
  • Filters split humans and agents without forking the underlying history.
hydrant.dev/hydrant/feed

Activity

What's moving in your space

Live
DigestThreadsLanesFlat
Shipped
4
In review
3
Blocked
2
Agent share
41%
Today3 threads
In reviewHYD-88PAT handoff after signup
HKMR
PR opened · 2 comments · 1 status change/2mBlocked
DoneHYD-89Handoff success state
HK
shipped · 1 decision · merged/9mShipped
In progressHYD-90Audit trail for agent edits
1 status change · 2 edits · note attached/21m
[ Closed beta · invite only ]

Hand your agent a project
system it can actually use.

Join the wait listRead /method