Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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 Aufrufe • vor 3 Monaten •via X (Twitter)

9 Kommentare

Profilbild von James
Jamesvor 3 Monaten

@OpenHandsDev @thsottiaux some ideas for the next iteration?

Profilbild von AI Mastery Guide
AI Mastery Guidevor 3 Monaten

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

Profilbild von unchosen.eth
unchosen.ethvor 3 Monaten

@OpenHandsDev efficiency will matter more over time

Profilbild von RF北灰
RF北灰vor 3 Monaten

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

Profilbild von atomic.chat
atomic.chatvor 3 Monaten

@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

Profilbild von RF北灰
RF北灰vor 3 Monaten

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

Profilbild von zhu
zhuvor 3 Monaten

@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

Profilbild von Engel Nyst - open/acc
Engel Nyst - open/accvor 2 Monaten

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.

Profilbild von Jeff Steve
Jeff Stevevor 3 Monaten

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

Ähnliche Videos