Alternatives
Products that do what Lific: Issue trackers should be simple, right? does
I built Lific because I direct AI coding agents on largish projects and needed somewhere for project state to live that isn't markdown files in the repo. When I was begging to work on long horizon ideas, I started on Linear, but my agent files issues faster than a human does, and I hit their limits and pricing wall almost immediately. Then I self-hosted a popular open source tracker which meant running its 13 containers, and its MCP integration was 30k tokens and I got so fed up that I eventually removed it and went back to .md files for a few weeks. Lific is the opposite shape of most of…
- 1PM
I built a lightweight project management workflow to keep AI-driven development organized. The problem was that context kept disappearing between tasks. With multiple Claude agents running in parallel, I’d lose track of specs, dependencies, and history. External PM tools didn’t help because syncing them with repos always created friction. The solution was to treat GitHub Issues as the database. The "system" is ~50 bash scripts and markdown configs that: - Brainstorm with you to create a markdown PRD, spins up an epic, and decomposes it into tasks and syncs them with GitHub issues - Track…
2025 · github.com
- 2GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 3IR
I've been running long duration coding agents with Claude Code for about 6 months now. Steve Yegge released Beads back in October and I found that giving Claude tools for proper task tracking was a massive unlock. But Beads grew massively in a short time and every release made it slower and more frustrating to use. I started battling it several times a week as its background daemon took to syncing the wrong things at the wrong times. Over the holidays I finally ripped it out and wrote ticket as a replacement. It keeps the core concept I actually cared about (graph-based task dependencies)…
Jan 2026 · github.com
- 4
- 5TM
Figured I'd track the popular coding agents to see merge and approval rates. At first I was tracking Opened vs. Approved, but realized most people aren't approving; they just merge. I haven't found a way to reliably track the other agents (Jules, Devin, etc), since they don't have a standardized branch naming convention. Interesting to watch this over time. Open to ideas.
2025 · github.com
- 6TT
I use multiple AI tools for work and also my side projects, and the annoying part was to track my costs and token usage across tools. Everytime I had to visit each tool and its respective usage setting to check it and I was losing patience and also was getting hit by surprise limits Now I know that there are already free/open-source trackers for Cursor or Claude usage, and they are useful if that is all you need. My problem is broader as I wanted one small place to see tokens, spend, subscriptions and limits across the AI tools I actually use. I was really tired of switching tabs and…
Jul 2026 · lifehacksgermany.com
- 7AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
- 8
- 9IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 10IB
Hi! My name is Herve Kom, a computer science student that is interested in learning new things everyday! As one of my graduation project, I have developed a Claude Code -like Coding CLI, but with enhancement for API Testing: - Auto-generate & run tests (unit, e2e, Playwright, CI/CD, etc.) - Say bye-bye to hallucinations with built-in MCP Server to let LLM directly read from API Docs - Adding Agent.md support for better context persistence across your whole codebase - Automatic bug & security scans (logic is kind of basic but works great!) - Vibes, I want it to feel less "enterprise" but…
2025 · github.com
- 11WV
Hi HN, I'm the CEO at https://replay.io. We've been working on time travel debugging for web development for a while (https://news.ycombinator.com/item?id=28539247) and more recently an AI app builder that uses that debugger to get past problems instead of spinning in circles (https://news.ycombinator.com/item?id=43258585). We've gotten to where we can pretty easily build apps to replace business-critical SaaS tools, some of which we're now using internally: * We built our own issue tracker to keep track of all our development projects, tickets, bug…
Dec 2025
- 12SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 13
- 14FA
Hi HN, Lately Github PRs have been drowning in a flood of AI slop. I’ve been seeing it myself, and I’m not the only one: https://x.com/mitchellh/status/2011819428061855915 I think it’s great that folks are using AI tools to code faster and better, but too many folks are abusing them to make low-quality contributions to public repos. This takes a lot of reviewers’ mindshare. IMO there needs to be a mechanism to flag low-effort PRs with AI slop, so you can just skip reading them. So I built one: https://haystackeditor.com/slop-detector It’s a simple AI…
Jan 2026 · haystackeditor.com
- 15AS
Hi, this is my first npm package that is getting a couple of hundreds downloads. It's a super simple CLI time tracker, mostly suitable for 9 to 5 jobs I hope you check it out and tell me what you think. Demo and etc. https://github.com/omidfi/moro
2017
- 16WR
Hi HN, I previously wore SWE/SRE hats on GCP. Later, I was on the other side, managing thousands of machines. The friction points of onboarding and operating cloud systems are personal problems to me. I’ve found it hard to keep track of all the random cloud resources floating around, especially as my team’s assets proliferated. Occasionally, there is a resource affecting an outage but no one remembers where it is. I am constantly frustrated by existing tooling. APIs can work, after you’ve navigated the byzantine documentation, but I often find myself doing ad-hoc tasks which are best…
2022 · listvms.com
- 17CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 18SM
I built this because I got tired of watching Claude Code read through massive files just to find a few functions. Sourcerer lets AI agents search code semantically and grab exactly the code chunks they need instead of burning tokens on whole files. It uses tree-sitter to parse your codebase and creates a searchable index. So instead of "read auth.py (538 lines)", an agent can search for "user authentication logic" and get back just the relevant functions. Demo: https://asciinema.org/a/736638 GitHub: https://github.com/st3v3nmw/sourcerer-mcp
2025 · github.com
- 19WB
Hey HN: Kaveh here, founder of https://www.usage.ai/ We help companies drive down AWS, GCP, and Azure spend. Why? Because the way it's done now is a pain. DevOps and Software Engineers end up spending time managing costs rather than focusing on business problems. I have been building Usage AI for almost 4 years now (4 year anniversary in 1 month from now!) with an incredible group of founding people. We started as a product just to help lower AWS EC2 costs, and now we do all major AWS services (such as RDS, OpenSearch, ElastiCache, and Redshift with more on the way) and other…
2024
- 208B
Hey all, Justin here. I previously built Phind, the AI search engine for developers. One of the biggest problems we had there was figuring out what went wrong with bad searches. We had tons of searches per day, but less than 1% of users gave any explicit feedback. So we were either manually digging through searches or making general system improvements and hoping they helped. This problem gets harder with agents. Traces are longer and more complex. It takes more effort to review them, so I'm building a tool that lets you analyze LLM outputs directly to help developers of LLM apps and agents…
Jan 2026 · trails-red.vercel.app
- 21NT
I built a CLI tool that turns codebases and PRs into diagrams so you can quickly understand how things fit together. Originally made it because I couldn't follow my own AI-generated repos. Just shipped a big update: - Switched from D2 to Mermaid for rendering - Tree-sitter AST parsing + agentic flow instead of raw LLM calls. ~50x faster. - Works on any GitHub repo or PR, not just local - Dropped the web frontend, it's just a CLI now - Published as a pip package Still a ton to improve and I'm building fast. Feedback, issues, PRs all welcome.
Feb 2026 · github.com
- 22IB
Hey HN. I built an AI agent harness over the past few months and I'm open sourcing it today. Some context on why. I've been building with Claude Code daily using this harness. It orchestrates multiple AI agents as a team, with a dashboard, chat, kanban board, the works. I used it to build a full SaaS product (MyUpMonitor, https://myupmonitor.com) in about 24 hours of focused coding. Then yesterday Anthropic announced Mythos and decided to keep it behind closed doors. Meanwhile I'm paying for Claude and I can't access their best model. I don't think that is nice at all... So I'm…
Apr 2026 · github.com
- 23
The Issue Tracker, built for speed
Jul 2026 · perplexed.site
- 24IB
I’ve spent the last 2.5 months building a product that runs LLM-powered code reviews on my pull requests — and I just launched it. The tool is built specifically for solo developers. You install it on your repo, trigger a scan by creating a pull request, and it leaves structured review comments using OpenAI under the hood. Funnily enough, I used the dev version of this app to review its own pull requests while building it. It helped me spot bugs, simplify structure, and keep quality high — all with minimal need for another human in the loop. Things I want to try out in the next months : -…
2025 · codii.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →