Show HN: Runner – the anti-vibe coding agent
IDEs were not built for this workflow. So about three months ago I decided to try to build what I thought this new interface should look like.
Runner is a coding agent purpose-built for this new “plan and review” workflow. It’s not for vibe coding. It’s for professional software developers who are responsible for the code they ship.
It encourages and supports a more structured and controlled workflow than other coding agents. It’s built around the concept of tasks. A task is a small, clearly scoped change. The planning agent creates and edits task specs, and then you can assign them to coding agents once you’re happy with the plan. When the coding agent finishes, you can review the changes via the built-in diff viewer. If you’re happy with them you can approve the changes, which will trigger a git commit.
Runner is available as a free BYOK beta for MacOS right now. You can learn more and download it here: https://runnercode.com/. You will need at least a Gemini API key, and for best performance also an OpenAI API key.
A persistent issue I have with Cursor et al. is that they hallucinate function arguments when using a function or method from a library. It seems like automatically pulling the library's documentation into the context would be helpful, but I haven't found any tool that does this automatically. Is there any chance that Runner does this?
It doesn't seem like this was the problem you were trying to solve, but reliable use of libraries and APIs is a critical problem to solve if you want LLM-generated code to work.
Could you explain why both / why not also Claude (why not all three?)