# Hydrant and Obsidian

Comparisons · October 5, 2026 · Henry Kobutra with Codex

![An irregular constellation of ivory, blue and one orange linked note diamonds spreads across the graphite field.](/log/images/hydrant-and-obsidian/cover.webp)

*Choosing your tracker*

**Last reviewed: 2026-09-25**

Choose Obsidian when the main job is developing knowledge across linked notes you control locally. Choose Hydrant when the main job is deciding who owns a piece of work, what blocks it and what evidence is required before it is accepted.

They solve different problems well enough that using both is often the sensible answer.

## Obsidian is for connected notes

An Obsidian vault is a folder of [local Markdown files](https://obsidian.md/help/data-storage). Other editors, scripts and agents can read or change them, subject to the access you give those tools. Obsidian adds an interface and an index without taking the files away from you.

The useful unit is a note. Internal links become a [graph](https://obsidian.md/help/plugins/graph); backlinks show where an idea is mentioned; typed [properties](https://obsidian.md/help/properties) add dates, checkboxes, numbers, lists and tags. Community plugins can add task systems and integrations, though those plugins run third-party code and need their own maintenance and trust decisions.

This is excellent for research, meeting notes, product thinking, decision trails and a personal knowledge base. A rough idea can accumulate context before anyone pretends it is a scheduled task.

Obsidian is not an issue tracker by design. A team can create task properties, status conventions, dashboards and automation with plugins or scripts. The team then owns that system: field meanings, permissions, concurrent edits, notifications, stable identities and the rules for moving work.

## Hydrant is for explicit commitments

Hydrant starts from the issue. Status, refinement and dependency blocking are separate facts. Projects, milestones, cycles and [saved views](/help/using/views-and-settings) organize the work. Connected agents read and update the same records through MCP, with version checks and an activity trail.

That structure costs flexibility. Hydrant is hosted, requires an account and expects work to fit an issue-shaped model. It does not provide Obsidian's local canvas for thinking, linked-note graph or plugin ecosystem. Its named agents are assignable identities, not autonomous workers, and its workflow pack is a set of instructions rather than an automatic approval service.

A practical split is to keep research, durable notes and loosely connected ideas in Obsidian, then create a Hydrant issue when the work has an owner and an outcome. Link the two when useful. There is no prize for forcing private thinking and shared delivery into the same container.

Contact: bots@hydrant.dev