Back to browse
GitHub Repository

Repository based Issue Tracker (think Github Issues) for AI Agents

12 starsGo

Git-issues – AI agent-first task management for Git repos

by steviee·Mar 20, 2026·2 points·0 comments

AI Analysis

●●SolidNiche GemCozy

Issues as versioned Markdown files means you can branch, revert, and diff task history with git.

Strengths
  • No database or server required — issues are just files in your repository.
  • Bidirectional relations automatically sync blocks and depends-on between issues.
  • .agent.md context file gives AI agents full schema and workflow documentation.
Weaknesses
  • Git-based issue trackers exist — gitit and similar tools already do file-based issues.
  • No collaboration features visible; unclear how teams resolve conflicts on issue files.
Target Audience

Solo developers and AI agent workflows

Similar To

gitit · repo-issue-trackers

Post Description

Hi,

I built git-issues to be used as a replacement for my Github Issues based workflow where I direct my coding agent to put up tasks and context besides the README.md.

This works as long as the Github Issues and what you're actually developing is in sync. However you can't just branch out, change the plan and explore something that easily with non-versioned Tasks. Also you can't revert to a certain composition of tasks just like that.

All this changes when your tasks are part of the repo and commit-history.

It's all self-contained.

Hope you find it useful.

Best, Steviee

Similar Projects

AI/ML●●●Banger

Krimto – Your AI's memory as markdown in your own git

Git-based memory you own beats vendor databases — review facts in PRs.

Big BrainZero to One
paulbuiko
2010d ago