This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
kadence
Git-native task journal your team and AI agents both read
Tasks, their whole history and the time they took live in your git repo as an append-only journal: one JSON file per event, never edited, never deleted. Everyone else keeps state — a task file, a row, a spec. State drifts, conflicts on merge and forgets. Events cannot: board and velocity are folded from the journal on read. Your team reads it in the terminal, your AI agents read the same thing as --json. No server, no account, no network. MIT.
Hi Product Hunt 👋
I work with coding agents every day, and the expensive part was never the code -
it was re-explaining. Every new session, my agent re-read the same files and
proposed the approach we had rejected last week. My teammate's agent knew none of
it either: that memory is per user, per machine.
So kadence keeps the missing layer in the repository itself - an append-only
journal, one JSON file per event, committed next to the code. Nothing is edited
or deleted, so `kadence task show KAD-1` can answer "how did we get here", and
`--json` hands an agent the same answer in about a kilobyte whether the project
holds ten tasks or a thousand.
Two things I would rather say up front than have you find out:
• Because it is append-only, two people editing one task on two branches is not a
merge conflict. We measured 8,396 merge commits across 130 public repositories
using file-based trackers before building on that claim - 15% of them hit
conflicts in task files, and 89% are the exact type a journal removes.
• What we have NOT proved is that teams lose enough context between sessions to
want a journal for it. That bet rests on reasoning, not on users - the interviews
are not run yet. If it turns out agents do fine with `git log`, the thesis falls.
MIT, free, zero network requests. Leaving costs `rm -rf .kadence` - your events
are plain JSON, readable without us.
What I would most like from you: if you work with agents in a team, tell me what
your last session had to relearn. That is the thing I am trying to kill.
npm install -g kadence && kadence init
About kadence on Product Hunt
“Git-native task journal your team and AI agents both read”
kadence was submitted on Product Hunt and earned 7 upvotes and 2 comments, placing #37 on the daily leaderboard. Tasks, their whole history and the time they took live in your git repo as an append-only journal: one JSON file per event, never edited, never deleted. Everyone else keeps state — a task file, a row, a spec. State drifts, conflicts on merge and forgets. Events cannot: board and velocity are folded from the journal on read. Your team reads it in the terminal, your AI agents read the same thing as --json. No server, no account, no network. MIT.
On the analytics side, kadence competes within Task Management, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how kadence performed against the three products that launched closest to it on the same day.
Who hunted kadence?
kadence was hunted by Andriy Bohutskyy. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of kadence including community comment highlights and product details, visit the product overview.
Andriy Bohutskyy