Issu Review (2026): Pricing, Features & Honest Verdict

TLDR

Issu is a CLI-based issue tracker that stores your tasks as markdown files inside your git repo, with an AI resolver and a Pomodoro timer for time logging. It is clever for solo developers but narrow for teams. Best for: solo devs who never want to leave the terminal. Price: free up to 100 issues, paid is custom. Rating: 6.2/10.

What is Issu?

Issu is an issue tracker for developers who would rather not open a browser. Instead of living on a web platform, it stores issues as markdown files directly inside your code repository. That means your issues version alongside your code, travel with the repo, and work offline. You manage them from the command line, and Issu adds a few extra touches: prioritization through ranking and labels, an AI resolver that uses your code context, and a built-in Pomodoro timer that logs time against each issue.

The product is clearly aimed at a specific kind of developer: someone who values keeping everything in one place, in plain text, under version control, and who treats the terminal as home base. We dug into it because local-first, in-repo issue tracking is a small but passionate niche, and Issu is one of the more polished recent attempts at it. The site is actively maintained with a 2026 copyright, live docs, and download links, so this is not an abandoned side project. It is a real, current tool, just a young and narrow one.

What Are Issu’s Key Features?

Markdown issues in your repo

The core idea is that issues are markdown files committed to your repository. They version with your code, so a feature branch can carry its own issue history and that history merges back in along with the code. There is no external service to go down and nothing to back up separately, because your issues are already in git. For developers who already keep notes, ADRs, and docs in markdown, this feels completely natural and removes a moving part from their stack. The trade-off, and it is a real one, is that the model gets unwieldy once several people are editing the same files at once, because you can end up resolving merge conflicts in your issue tracker.

CLI-first workflow

Issu is driven from the command line. You create, rank, label, and prioritize issues without leaving the terminal, which keeps you in flow if that is where you already work. There is no tab to switch to and no web app to load, so the friction of logging a quick issue mid-task drops to almost nothing. Download links and documentation are available on the site. For anyone who lives in their editor and shell, removing the browser context switch is the main draw, and it is the feature that will either sell you instantly or not at all.

AI-powered issue resolution

Issu includes an AI resolver that leverages issue metadata and the surrounding code context to help work through issues. Because the issues sit next to the code in the same repo, the AI has more context to draw on than a generic web tracker bolted onto an API would. How much this actually saves you will depend on the complexity of your issues and your codebase, and it is not going to fix hard bugs for you, but the integration is a sensible use of the in-repo design rather than an AI feature stapled on for marketing.

Pomodoro timer with auto time logging

A built-in Pomodoro timer lets you run focused work sessions and automatically logs the time against the issue you are working on. It is a small feature, but it folds time tracking into the same tool you are already using, which beats juggling a separate timer app and copying numbers by hand. For freelancers who bill by the hour or solo devs who just want to know where their time went, having the timer attached to the issue is a genuinely useful touch.

How Much Does Issu Cost?

Issu starts free. The free plan gives you 100 issues, 10 labels, and community support at no cost, which is enough for a solo developer or a small repo to run for a long time. For many indie projects and personal repos, the free tier may honestly be all you ever need, and there is no time limit forcing you off it.

The paid Unlimited plan removes the issue and label caps and adds responsive human support and prioritized feature requests. The catch is that its price is not published anywhere we could find: you have to contact the team to learn it, including for custom options like SLAs or professional services. That is a real friction point compared to competitors. Linear publishes a clear $10 per user per month Basic plan, and GitHub Issues is free with any GitHub account.

For budgeting purposes, treat Issu as free until you hit the limits and then as an unknown you have to ask about. That uncertainty is fine for a hobby project but awkward for a team that needs to plan spend or get a number approved before adopting a tool. It also makes a fair head-to-head comparison hard, since you cannot weigh Issu Unlimited against a known Linear seat price without picking up the phone.

Who is Issu Best For?

Use Issu if you are a solo developer or a tiny team that wants issues tracked in the repo as markdown, under version control, and managed from the command line. The free tier is generous enough to run a real project, the local-first design is genuinely useful offline or on a flaky connection, and the Pomodoro and AI touches fit the workflow well rather than feeling tacked on. If you already keep everything in plain text and resent leaving the terminal, this is built for you.

Skip Issu if you have non-technical stakeholders, a growing team, or a need for predictable pricing. Markdown-in-repo does not scale gracefully to many editors working at once, and product managers, designers, or clients are simply not going to live in a CLI no matter how elegant it is. If you need reporting, dashboards, assignment workflows, and a shared web view that anyone can open, GitHub Issues or Linear will serve you far better. Issu is a sharp tool for a narrow job, and using it outside that job will frustrate you.

It is also worth being honest about the pricing question mark. If you are the kind of buyer who needs to know the cost before adopting anything, the hidden Unlimited price is a genuine reason to wait or to pick a competitor that publishes its numbers.

Best Issu Alternatives

GitHub Issues

GitHub Issues is the obvious default: it is free with any GitHub account, integrates tightly with your code and pull requests, and everyone on a dev team already knows it. It is web-based rather than in-repo, so it lacks Issu’s offline and version-controlled angle, but it has a massive ecosystem and zero adoption friction. For most teams, this is the baseline to beat.

Linear

Linear is the polished, fast issue tracker that engineering teams love, starting at $10 per user per month with a free tier. It is the opposite philosophy to Issu: a slick web app with a local sync engine for speed, deep integrations, and a clear pricing page. If you want a real team tracker with roadmaps and reporting, Linear is the upgrade path.

git-bug

git-bug is the open-source, free alternative that shares Issu’s spirit most closely. It is a distributed bug tracker written in Go and embedded directly in git, so issues live in your repo and sync peer to peer with no server. It is more bare-bones and lacks the AI and Pomodoro extras, but if you want the local-first model for free with no pricing question marks, git-bug is the one to try.

Final Verdict: Is Issu Worth It?

Issu earns a 6.2 because the core idea is genuinely good but the execution is still narrow. Storing issues as markdown in your repo, managing them from the CLI, and logging time with a built-in Pomodoro timer is a clean fit for the developer who wants everything in one versioned place. The free tier is generous enough to make trying it a no-brainer for a solo project.

It does not score higher because of two real limits. The markdown-in-repo model does not scale to teams or non-technical stakeholders, and once more than a couple of people are editing issues you trade the convenience for merge conflicts and confusion. The paid Unlimited plan also hides its price behind a contact form, which makes it hard to evaluate against competitors that publish clear numbers, and that opacity is a strange choice for a tool aimed at independent developers who tend to want to self-serve. Those two issues cap how broadly we can recommend it.

That said, within its niche it is a pleasure. If you are a solo developer who hates leaving the terminal and already keeps your life in plain text and git, give the free plan a spin, because it costs nothing and the workflow either clicks for you immediately or it does not. If instead you need a team tracker with predictable costs, assignments, and a shared web view that everyone can open, GitHub Issues or Linear is the safer and more capable call. Issu is a well-made tool that knows exactly who it is for, and the 6.2 reflects how narrow that audience is rather than any sloppiness in the build.