A task tracker and wiki built for teams whose work is increasingly done by AI agents. It speaks the API of the tracker most companies already run, so the MCP servers your agents use work unchanged. Built-in MCP server for Claude Code and Cursor, agents you call in a comment that propose but never decide, and every agent run's cost recorded on the issue it worked on.
Hi Product Hunt 👋
Kaiku started from a simple annoyance: coding agents are good at the work, but everything around it — filing the issue, writing down what was decided, knowing what the automation cost — still fell on a person.
So Kaiku is a task tracker and a wiki designed with agents as first-class users:
• It speaks the REST API of the tracker and wiki most companies already run, so the MCP server your agent already has works unchanged.
• It has its own MCP server too — connect Claude Code or Cursor in one line.
• Built-in agents you call in a comment. They answer with what they read, run on the caller's access, and never decide: a proposal is a question for a person.
• Every agent run is recorded on its issue: tokens, machine time, who asked.
• Your data stays yours: export a whole project in one request, even after a subscription ends.
Also inside: boards and sprints, a mini-CRM (a table of clients with the work under each), a calendar that only draws what was actually recorded.
30 days free, no card. I'll be here all day — ask me anything.
Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?
The cost-on-the-issue part is what I'd want most. I run a bunch of scheduled agent jobs for a small job board (posting, moderation, a daily article), and the expensive surprises were never one big run, they were duplicates. My laptop slept through a few slots, the scheduler caught up on wake and the same job ran twice, so two identical posts went out and nobody noticed until a reader did. What fixed it was boring: each job reads a small log of what it already did today before touching anything. If an agent picks up the same Kaiku issue twice after a retry, does the second run see the first one's record and stop, or does it just log a second cost line next to it?
About Kaiku on Product Hunt
“The task tracker your AI agents already know how to use”
Kaiku launched on Product Hunt on September 25th, 2026 and earned 76 upvotes and 2 comments, placing #16 on the daily leaderboard. A task tracker and wiki built for teams whose work is increasingly done by AI agents. It speaks the API of the tracker most companies already run, so the MCP servers your agents use work unchanged. Built-in MCP server for Claude Code and Cursor, agents you call in a comment that propose but never decide, and every agent run's cost recorded on the issue it worked on.
Kaiku was featured in Task Management (84.3k followers), Developer Tools (520.1k followers), Artificial Intelligence (479.5k followers) and Vercel Day (40 followers) on Product Hunt. Together, these topics include over 221.8k products, making this a competitive space to launch in.
Who hunted Kaiku?
Kaiku was hunted by Stanislav. 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.
Want to see how Kaiku stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Stanislav