Git-native task board built for AI coding agents

What to build

A git-native task board CLI + lightweight local web UI that stores tasks as plain markdown or YAML files inside a repo, so both developers and AI coding agents (Claude Code, Cursor, etc.) can read, create, and update tasks by editing files and committing, with no SaaS backend or account required.

Solo developers using AI coding agents need task state that lives where their agent already operates — in the repo — instead of behind a SaaS API their agent can't easily reach, and a Product Hunt launch (Bruto) shows builders are already experimenting with exactly this idea.

Demand

Solo developers and small teams running AI coding agents want their agent to be able to read and update the task list as part of normal file edits and commits, which today's hosted task boards don't support well; the demand is now rather than earlier because AI coding agents only recently became a daily driver for many solo builders.

• Product HuntLaunch

  Product Hunt listing for Bruto, described as 'A task board that lives in your repo, for you and your AI' — a live launch of a product built on this exact premise.

• Signal opportunity briefAnalysis

  Opportunity framed around AI coding agents being unable to easily query or update tasks stored outside the repo, motivating a file-based alternative.

• Signal metadataScore

  Signal scored 0.58 with no historical match found, indicating this is a novel, not-yet-recurring opportunity rather than an established trend.

Stack

• Node.js or Go CLI
• Markdown/YAML frontmatter as task schema
• libgit2 or shell git for commit/diff handling
• SQLite or in-memory index for fast local queries
• Local web server (Express/Fastify or Go net/http) for the viewer UI
• React or plain HTML/htmx for the local UI

Solo + AI difficulty

The CLI, file schema, and local web viewer are straightforward for one person with an AI agent to build in 1-2 weeks; the harder parts are designing a task file format that's both human-readable and reliably parseable by AI agents, and handling merge conflicts gracefully when multiple branches edit the same task files. MVP (CLI + basic viewer + git sync) is realistically achievable in under a month.

Entry threshold

Very low barrier: a solo builder can ship a CLI tool or VS Code extension plus a minimal local UI in days using a simple file format parser, packaging it as an open-source project or npm/pip package with an optional paid hosted sync or team view.

Window

3-6 months

Where to find first users

• Product Hunt launch
• Hacker News Show HN post
• r/ClaudeAI and r/cursor communities
• Indie hacker / AI coding agent Discord and Twitter/X communities

Competitors

• Bruto
• git-bug
• Taskwarrior
• GitHub Issues

Counter-signals & risks

• Plain-file task boards stored in git may not scale well for teams with many concurrent tasks, causing merge conflicts on shared task files and degrading the 'simple' value proposition.

• Existing tools (e.g., git-bug, GitHub Issues, Taskwarrior, org-mode, plain TODO.md conventions) already partially address git-native or file-based task tracking, raising differentiation risk.

• AI coding agents may already be able to read/write to SaaS task tools via APIs or MCP-style integrations, weakening the core premise that SaaS tools are inherently inaccessible to agents.