正在加载视频...

视频加载失败

OpenHands crushed Codex by 2.3× on token efficiency! We gave both agents the same task on the same model (Qwen3.5 35B): build an 8-bit Space Invaders in 3 iterations (build, fix, polish). Output: • OpenHands: 219K tokens, • Codex: 513K tokens, OpenHands beats Codex in local running. The difference...

29,842 次观看 • 3 个月前 •via X (Twitter)

9 条评论

James 的头像
James3 个月前

@OpenHandsDev @thsottiaux some ideas for the next iteration?

AI Mastery Guide 的头像
AI Mastery Guide3 个月前

@OpenHandsDev 2.3x fewer tokens for the same task is a big efficiency gap

unchosen.eth 的头像
unchosen.eth3 个月前

@OpenHandsDev efficiency will matter more over time

RF北灰 的头像
RF北灰3 个月前

@OpenHandsDev That’s mean the openhands can save tokens when i use it ?

atomic.chat 的头像
atomic.chat3 个月前

@OpenHandsDev for multi-step tasks like build/fix/polish loops -yeah, since it reuses context instead of resending it. one-off prompts, less so. depends what you're doing

RF北灰 的头像
RF北灰3 个月前

@OpenHandsDev Ok, I got it, it’s depends on the type ofmy task, thanks!

zhu 的头像
zhu3 个月前

@OpenHandsDev @grok explain what is that means "euses the unchanged data across every pass and only pays for new tokens, while Codex re-sends and re-counts it every iteration" and how it affects KV cache

Engel Nyst - open/acc 的头像
Engel Nyst - open/acc2 个月前

The explanation doesn’t make sense to me. Codex can and does normally send the prefix unchanged for prompt caching. So does OpenHands. The video shows 30 iterations on OpenHands side, 9 for Codex side, so it must be all Codex uncached. I think you guys have a bug of some kind on Codex / Codex config.

Jeff Steve 的头像
Jeff Steve3 个月前

@OpenHandsDev Hi still here asking for MCP support on atmoc chat on google play store like operit AI

相关视频