Загрузка видео...

Не удалось загрузить видео

На главную

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/acc3 месяцев назад

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

Похожие видео