Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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 görüntüleme • 3 ay önce •via X (Twitter)

9 Yorum

James profil fotoğrafı
James3 ay önce

@OpenHandsDev @thsottiaux some ideas for the next iteration?

AI Mastery Guide profil fotoğrafı
AI Mastery Guide3 ay önce

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

unchosen.eth profil fotoğrafı
unchosen.eth3 ay önce

@OpenHandsDev efficiency will matter more over time

RF北灰 profil fotoğrafı
RF北灰3 ay önce

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

atomic.chat profil fotoğrafı
atomic.chat3 ay önce

@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北灰 profil fotoğrafı
RF北灰3 ay önce

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

zhu profil fotoğrafı
zhu3 ay önce

@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 profil fotoğrafı
Engel Nyst - open/acc2 ay önce

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 profil fotoğrafı
Jeff Steve3 ay önce

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

Benzer Videolar