harnesses are becoming the new tech stack, I created my own and will compare it to how bullet operates, I’ve also built and deployed iOS and Android apps with my tool. When you have built something with the tool, other than the tool, it’s stronger proof.
Launch HN: Bullet (YC S26) – A Faster Coding Agent
51–60 of 93 posts
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#52Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#53Critical for the future of AI native products. Congrats on the launch!
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#54Please consider atleast adding MCP support if you can. That'll help
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#551. Model routing. Do you regret giving a task to Fable when it could have literally been done by Sonnet?
This is the one thing that I can understand.
2. Targeted code + context search. We think embedding the whole repo is dumb. We also think sticking the whole context (or compressed context) in chat is dumb. So we do faster and better greps over both.
Is this just a different system prompt? Why would other harnesses not be able to do it this way given instructions to do so?
3. Aggressive context hygiene. Tool output is bounded, stale screenshots disappear, we don’t re-read files…the garbage never floods the model.
Existing harnesses already don't re-read files that have not changed. And content that is already in the context window is cached tokens and doesn't add significant latency, what am I missing? Removing context from history invalidates KV cache.
4. Efficient turns. Batch independent investigation, make one surgical edit, then perform one focused verification. Internal measurement showed 16% fewer round trips and 27% lower cost.
Isn't this just a specific sub-agent strategy, also addressable with prompting?
I'm genuinely confused about what is mechanically different in this harness that could not be accomplished with a prompt/skill in another harness.
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#56Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#57Hey just some feedback. I'm giving it a try on a new project I'm spinning up. It does seem faster although I haven't timed it against Claude or anything. I like the integrated browser to immediately see the changes (or see what the agent is doing). Thanks for having Linux support.
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#58I use codex cli. It doens't have a UI for linux. I use opencode for that but it doens't work that well with the new 5.6 model suite from openai. Codex is both faster and better. I would have loved if there was a way to use a GUI that worked like codex. Gave this a try. I think this might be it. Please consider atleast adding MCP support if you can. That'll help
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#59I use codex cli. It doens't have a UI for linux. I use opencode for that but it doens't work that well with the new 5.6 model suite from openai. Codex is both faster and better. I would have loved if there was a way to use a GUI that worked like codex. Gave this a try. I think this might be it. Please consider atleast adding MCP support if you can. That'll help
"Codex in ChatGPT desktop app for Linux is now in preview" https://community.openai.com/t/codex-in-chatgpt-desktop-app-...
Re: Launch HN: Bullet (YC S26) – A Faster Coding Agent
#60harnesses are becoming the new tech stack, I created my own and will compare it to how bullet operates, I’ve also built and deployed iOS and Android apps with my tool. When you have built something with the tool, other than the tool, it’s stronger proof.
Agree, building real apps with the harness is the strongest proof. Would love to hear where Bullet fell short vs your setup, especially on speed for your builds.
My coding agent leverages vector search and grep, just using grep takes longer and seems more expensive per task.