01 / THE SIGNAL

我们发现了什么

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
#开发效率#付费线索#产品发现
02 / SOURCE & EVIDENCE

证据,比故事更重要。

存在定价或订阅线索;有收费设计不等于已有收入。

规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。

引用与数字披露

来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。

短句引用
作者
未标注
抓取日期
来源类型
未标注
数字口径
币种
未标注
口径
未标注
披露主体
未标注
披露日期
未标注

上下文核对:来源原文含限定词一次性,中文摘要未逐字保留 —— 引用或跨期比较前请回原文核对,别把估算读成已实现。

中文辅助译文(全文)

嗨 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. 模型路由。你是否曾后悔把一个任务交给了 Fable,而它本可以由 Sonnet 直接完成?2. 定向代码 + 上下文搜索。我们认为对整个仓库做嵌入很愚蠢。我们同样认为把整个上下文(或压缩后的上下文)塞进聊天里也很愚蠢。

因此我们在代码与上下文上做更快、更好的 grep。3. 激进的上下文卫生。工具输出有界、过期截图被清除、不重复读文件……垃圾永远不会淹没模型。4. 高效回合。批量处理独立调查、进行一次精准编辑,然后执行一次聚焦验证。内部测量显示往返次数减少 16%、成本下降 27%。5.The Flash。我们向 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 的一些点,但我们每天都在持续优化(瞧,看来我们确实从以前的工作中学到了一些东西)。在我们的开发过程中,最大的洞见是模型速度的重要性低于减少往返次数。独立的搜索、读取和命令应当并行执行,而依赖性的编辑与验证则保持顺序。一个意想不到的障碍是代码搜索,像正则方言不匹配这样的小问题会导致静默漏检……

译文由上游机器翻译生成,可能有误;判断请以英文原文为准。

英文原文(来源本站未改写)

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 s

出处https://codewithbullet.com抓取日期 · 采集源 Hacker News

03 / EVIDENCE GAPS

这条还缺什么证据?

下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。

  • 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
  • 商业模式未定确认按席位/按用量/授权还是开源托管版收费;开源项目另查 LICENSE 与是否存在付费版。
  • 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。

通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法

04 / SIGNAL HISTORY

发现时间线