Launch HN: Bullet (YC S26) – A Faster Coding Agent
Launch HN: Bullet (YC S26) – A Faster Coding Agent
我们发现了什么
So, Bullet started as an AI hedge fund, a browser-use agent, synthetic financial data (oof), a mobile IDE, and a bunch of other things.
- 来源:Hacker News(发现于 2026-08-14)
- 证据等级:C · 存在定价或订阅线索;有收费设计不等于已有收入。
- 商业模式:待核验
- 主题:开发者工具
- 初筛评分:16/100 · 收录 1 次
证据,比故事更重要。
规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。
引用与数字披露
来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。
- 作者
- 未标注
- 抓取日期
- 来源类型
- 未标注
- 币种
- 未标注
- 口径
- 未标注
- 披露主体
- 未标注
- 披露日期
- 未标注
中文辅助译文(全文)
嗨,HN!我们是 Adi 和 Alex,Bullet 的创始人,Bullet 是一个更快的编程代理。Bullet 起源于大四的宿舍。我们刚从 AppLovin 和 Citadel 离职,自然而然地以为自己走上了创业成功的康庄大道。我们打算用优化股票定价计算速度和代理文档上下文的技能来征服世界。因此,Bullet 最初是一个 AI 对冲基金、一个浏览器使用代理、合成金融数据(哎呀)、一个移动 IDE,以及其他一堆东西。我们想打造人们需要的东西,但似乎我们做的所有东西都很糟糕、无用,或者两者兼而有之。所以,我们决定做一些完全不同的事情,一些完全出人意料的事情,一些前所未有的事情——解决我们真正遇到的问题。在六次转型的过程中,我们吃尽了苦头。在我们所有的冒险历程中,总有一个最终 Boss 挡在我们的路上:Claude Code 和他的小兄弟 Codex。我们花费数小时等待 Claude Code 和 Codex 这样的编程代理,沮丧到极点,我甚至下载了 Claude Code 的鞭子。我们花了数月时间等待相当于六个代码库的无用编程代理工作。灵光一现。没有什么比摧毁旧制度更高尚的了!让我们来挑战 Claude Code 和 Codex,我们能做到!小菜一碟!就这样,Bullet 最初是作为一个业余项目开始的。我们用 Claude Code 来改进 Claude Code:1. 模型路由。当一个任务明明可以用 Sonnet 完成时,你是否后悔把任务交给了 Fable?2. 针对性的代码 + 上下文搜索。我们认为对整个仓库做嵌入很愚蠢。
我们也认为把整个上下文(或压缩后的上下文)塞进聊天窗口很愚蠢。所以我们对两者都进行了更快、更好的 grep。3. 激进的上下文卫生管理。工具输出有界,过时的截图会消失,我们不重复读文件……垃圾信息永远不会淹没模型。4. 高效的回合。批量进行独立的调查,进行一次精准的编辑,然后执行一次集中的验证。内部测量显示回合数减少了 16%,成本降低了 27%。5. 闪电。我们向 Barry Allen 祈祷速度。感谢闪电侠,他赐予了我们速度!在 SWE-bench Verified 上,Bullet 一次尝试解决了 479/500 (95.8%) 的问题,平均每个任务 119 秒,根据任务不同,比 mini-SWE-agent + Fable/Sol 快 35–67%。完整结果和方法论见此处(https://www.codewithbullet.com/blog/benchmark-results.html )。最终我们开始每天使用它,再也没有回头。上面列出的只是 Claude Code 最让我们沮丧的一些地方,但我们每天都在不断优化(瞧瞧,也许我们确实从工作中学到了一些东西)。在我们的开发中,最大的洞察是模型速度的重要性不如减少回合数。独立的搜索、读取和命令应该并行执行,而依赖性的编辑和验证则保持顺序执行。一个令人意外的障碍是代码搜索,正则方言不匹配这样的小问题会导致静默漏检,让代理走上完全错误的路径,因此我们构建了带有回退机制和有限上下文的针对性搜索。到目前为止,最有趣的用例是长时间的迭代工作(如基准测试、数据管道和评估循环),其中每一步都依赖于上一步,运行多个代理并不能提供太多帮助。
视频演示见此处(https://www.youtube.com/watch?v=rWVmG5fRKgE )。我们希望大家能试试 Bullet,如果你们和我们一样为速度所困扰,希望它能带给你们快乐、彩虹和更快的响应。如果它很糟糕,请告诉我们它很糟糕(顺便说一下,我们是受虐狂)!我们整天都会泡在评论区,你也可以通过 bullet@davidhf.com 与我们联系。你可以在 https://codewithbullet.com 试用。附:我们在网站上藏了一个代码,看看你能否在页脚解锁秘密页面,全部用 Bullet 构建。
译文由上游机器翻译生成,可能有误;判断请以英文原文为准。
英文原文(来源本站未改写)
Hi HN!We’re Adi and Alex, founders of Bullet, a faster coding agent.Bullet started in a senior year dorm.We were fresh out of working at AppLovin and Citadel, and naturally thought we were on a sure path to startup success.We were going to use our skills optimizing stock pricing calculation speeds and agent document context to take over the world.So, Bullet started as an AI hedge fund, a browser-use agent, synthetic financial data (oof), a mobile IDE, and a bunch of other things.We wanted to build something people wanted, but it seemed like everything we built was just terrible, useless, or both.
So, we decided to do something completely different, something completely out of the blue, something that no one had ever done before.Solve a problem we actually had.Over the course of six pivots, we suffered.Throughout all of our adventures, one final boss kept getting in our way.Claude Code and his little brother Codex.We were spending hours waiting for coding agents like Claude Code and Codex, and got so frustrated to the point that I downloaded the Claude Code whip.We had spent months of time waiting for six codebases-worth of useless coding agent work.Lightbulb moment.There’s nothing more noble than destroying the institutions!Let’s take on Claude Code and Codex, we can do it!
Piece of cake!And so, Bullet started off as a side project.We used the Claude Code to improve the Claude Code: 1.Model routing.Do you regret giving a task to Fable when it could have literally been done by Sonnet?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. 3.Aggressive context hygiene.Tool output is bounded, stale screenshots disappear, we don’t re-read files…the garbage never floods the model. 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. 5.The Flash.We prayed to Barry Allen for speed.And thank the Flash, he gave us speed!On SWE-bench Verified, Bullet resolved 479/500 (95.8%) in one attempt, averaging 119s per task, 35–67% faster than mini-SWE-agent + Fable/Sol depending on task.Full results and methodology here ( https://www.codewithbullet.com/blog/benchmark-results.html ) Eventually we started using it every day and never went back.Listed above were just some of the things about Claude Code that frustrated us the most, but we are constantly optimizing every day (look at that, maybe we did learn something from our jobs).
In our development, the biggest insight was that model speed matters less than reducing round trips.Independent searches, reads, and commands should happen in parallel, while dependent editing and verification stay sequential.One surprising obstacle was code search, small issues like regex-dialect mismatches caused silent misses and sent agents down completely wrong paths, so we built targeted search with fallbacks and bounded context.The most interesting use case so far has been long iterative work (like benchmarks, data pipelines, and evaluation loops), where each step depends on the last and running multiple agents can’t help as much.Here’s the video demo ( https://www.youtube.com/watch?
v=rWVmG5fRKgE ) We hope that you guys try out Bullet if you are suffering with speed as much as we were, and we hope it brings you joy, rainbows, and faster responses.And if it’s terrible, let us know it’s terrible (we’re masochists btw)!We'll be in the comments all day, you can also contact us at bullet@davidhf.com.You can try it at https://codewithbullet.com .P.S: we hid a code on the website, see if you can unlock the secret page at the footer, all built with Bullet
这条还缺什么证据?
下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。
- 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
- 商业模式未定确认按席位/按用量/授权还是开源托管版收费;开源项目另查 LICENSE 与是否存在付费版。
- 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。
通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。