Alternatives
Products that do what Think Better does
Stop babysitting your AI.Inject 70 years of decision science
- 1TC
Hi HN, I'm thrilled to share with you think, a command-line tool that I developed while diving back into the programming scene. For the past few years, my focus had shifted from hands-on programming to managerial roles, my last one being at Affirm (I started Affirm's Polish office). However, I recently left my job to revisit my passion for coding and see if I could still write code that works. Not to mention that with what is currently going on in AI if you are a developer this probably the best possible time for a sabbatical in human history :) My first attempt was with LangChain, but I…
2023 · github.com
- 2WB
Hey HN, We’re two developers (co-founders) with a team of 20 who got tired of spending hours reviewing PRs, so we built Infinitcode.ai, an AI-powered code reviewer that: - *Summarizes PRs in plain English*: No more deciphering 1,000-line diff jungles - *Catches more than bugs*: Security holes, performance pitfalls, code smells, even typos (yes, we’ll flag “vurnerabilities” and vulnerabilities) - *Zero onboarding*: Works instantly—no “let me learn your codebase for weeks” nonsense. Why we’re posting: We’re in alpha and need brutal honesty. Roast our tool, mock our UI, or tell us why AI will…
2025 · infinitcode.ai
- 3
Cause "You're absolutely right" is probably absolutely wrong
Apr 2026 · npmjs.com
- 4OC
Jul 2026 · github.com
- 5
- 6IB
So, you know how bigtech gives nearly unlimited credits for coding tools and in the same time put a huge admin whitelist of what commands are allowed? So, instead of becoming a 100x engineers, you (including me) simply become a multi-window-enter-clicker I build a tool to solve this. It works locally, using OCR finds the "run" (or any other label you put e.g. accept, allow, fetch etc. ) and just clicks this button. Originally this was a tool for me and my team, but people seamed to love it so much, they encouraged me to share with you. I do understand that workflows in each bigtech company…
May 2026 · github.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
- 8OS
Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…
Jan 2026
- 9MA
Hello there HN I experimented with agentic coding recently and I felt the need to track more contextual data by project. Also I felt the need to be able to go beyond the 1D chat to communicate with agents. So I created a local document memory, that is discoverable by agents themselves. The CLI is designed to be easy to pick up by agents. It allows humans to collaborate too by reading / searching / editing documents in the store. I have a Mac native GUI in the review process, I hope it will show up in the App Store soon. You can try it easily, instructions here:…
Jun 2026 · metabrain.eu
- 10
- 11IB
TLDR; I built a tool that turns any API into a CLI designed for ai agents --- Got tired of dealing with bloated context windows from MCP servers and skills that stuff entire API docs into the agent's context CLIs fix this, agents run a single command to self-discover everything an API has to offer So, built a tool to generate them for any api. All CLIs are written in Go, fast and lightweight, no dependencies Help text (via the --help flag) is the killer feature: all context for each command/endpoint/parameter is extracted directly from the user-facing API docs and enhanced with…
Mar 2026 · instantcli.com
- 12WT
I've been lurking on HN for years. You know the drill: interesting headline, 200+ comments, you dive in thinking "I'll just skim for 5 minutes"... and an hour later you're 36 chambers deep in a thread about memory allocation patterns in Postgres and you've completely forgotten what the original article was about. I don't just want a "summary" (which usually just shortens the noise). I want the meta-consensus: "What is the actual trade-off being debated? Who is winning the argument? Why does this matter?" So I built HNSignals. Think of it less like a "summarizer" and more like a Chief of…
Jan 2026 · hnsignals.com
- 13AC
This week we released the Kodus CLI. It took a bit longer than we expected to ship. The reason was simple: there are already many ways to run reviews locally today. IDEs, extensions, terminal commands, agents inside the editor. So building “just another AI CLI” didn’t seem like a good idea. The question that guided the project was different: how can we bring the quality of PR reviews to the moment when the code is still being written? Today the CLI does two main things. The first is running local reviews using the same context we use in PRs. The goal was to avoid that shallow review that…
Mar 2026 · github.com
- 14IB
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
- 15
Your AI validates bad decisions. These tools challenge them.
Jun 2026 · reasoning.services
- 16IB
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
- 17IB
I've been experimenting with ways to increase AI adoption for non-technical people. Basically, all companies are pushing for AI because it's all over the news and they feel left behind but most people have no clue where to start. I think 90% of people (ie non coders) are sufficiently well served by using cowork instead of claude code or something similar. If we can get people from sales, customer support, marketing, etc to collaborate with skills and cowork to form a company brain, I think it's gold. So I think there's opportunity for the community to share skills that work well for 1000s of…
Jun 2026 · claudinho.xyz
- 18
- 19MC
Hi HN, I’ve been building AI agents and copilots, and kept running into a frustrating problem: they don’t fail loudly, they forget things quietly. Users re-explain preferences, agents contradict earlier responses, and context resets without any clear visibility into why. I built Memograph CLI as a debugging tool to analyze conversation transcripts and show: - what the agent forgot - where continuity broke - contradictions and repeated context - estimated token waste due to re-prompting It works locally and supports plain text or JSON transcripts. Example: $ memograph Output: Cognitive Drift…
Feb 2026
- 20NT
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
- 21IM
Every time I wanted to use LLMs in my existing pipelines the integration was very bloated, complex, and too slow. This is why I created a lightweight library that works just like scikit-learn, the flow generally follows a pipeline-like structure where you “fit” (learn) a skill from sample data or an instruction set, then “predict” (apply the skill) to new data, returning structured results. High-Level Concept Flow Your Data --> Load Skill / Learn Skill --> Create Tasks --> Run Tasks --> Structured Results --> Downstream Steps And the bast part: Every step can be saved and reused as…
2025 · github.com
- 228S
We made a dumb terminal for AI! Type \ to see commands you can use.
2025 · vt320.odai.chat
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →