Gezinmeyi atla
I tested Cursor Composer 2.5 vs OpenAI GPT-5.5 Medium Fast in a head-to-head coding speed test.
0:00 / 2:07

I tested Cursor Composer 2.5 vs OpenAI GPT-5.5 Medium Fast in a head-to-head coding speed test.

Zortos

@Zortosdev2,8 B takipçi

X profili
450 beğeniİndirOrijinal gönderi

101.273 görüntüleme

I tested Cursor Composer 2.5 vs OpenAI GPT-5.5 Medium Fast in a head-to-head coding speed test. Same prompt. Same task. Results: Composer 2.5: 43 sec GPT-5.5: 2 min 3 sec Composer finished faster, while GPT-5.5 took longer and made more tool calls.

42 Yorum

Yorumlar X (Twitter) üzerindeki orijinal gönderiden alınmıştır

  • Zortos profil fotoğrafı

    @Zortosdev

    Raw Prompt: # Stripe Discord Webhook Implementation Plan **Goal:** Build a Node.js Stripe webhook service that listens for successful payment events and sends Discord embed notifications with payment details. **Architecture:** Use Express with a raw JSON body on the Stripe webhook route so Stripe signatures can be verified safely. Keep payment event normalization, Discord embed construction, and server routing in separate modules so each piece can be tested directly. **Tech Stack:** Node.js, Express, Stripe SDK, Node built-in `fetch`, Jest, Supertest, dotenv.

    7 beğeni

  • Eyad Kelleh profil fotoğrafı

    @KellehEyad

    @cursor_ai @OpenAI Composer 2.5 hits differently, it has changed the flow

    6 beğeni

  • Zortos profil fotoğrafı

    @Zortosdev

    @cursor_ai @OpenAI Composer 2.5 hits different. It completely changed the flow. It’s so fast I don’t even have time to think about the next message before it’s already done.

    7 beğeni

  • Eyad Kelleh profil fotoğrafı

    @KellehEyad

    @cursor_ai @OpenAI Same feeling

    1 beğeni

  • Gregor profil fotoğrafı

    @bygregorr

    @cursor_ai @OpenAI ngl framing 'more tool calls' as a negative is the tell faster isn't better if it's skipping verification steps

    6 beğeni

  • Zortos profil fotoğrafı

    @Zortosdev

    That’s fair, but in this clip it wasn’t really “verification.” Codex first produced broken code for a simple task, then used extra tool calls to fix its own mistake. Composer 2.5 got it right in one shot. So the point isn’t “more tool calls = bad.” The point is Composer was faster while also needing less recovery work.

    12 beğeni

  • Zortos profil fotoğrafı

    @Zortosdev

    @OpenAI Subscriptions used: Cursor 20$ plan Codex Pro 200$ plan

    6 beğeni

  • Morgan profil fotoğrafı

    @morganlinton

    @cursor_ai @OpenAI Which output more accurate code?

    4 beğeni

  • J A Z I I profil fotoğrafı

    @notjazii

    @cursor_ai @OpenAI I couldn't even tell which one is composer and which one is Codex lmaoo

    3 beğeni

  • Zortos profil fotoğrafı

    @Zortosdev

    @cursor_ai @OpenAI so similar UI ngl

    3 beğeni

  • J A Z I I profil fotoğrafı

    @notjazii

    @cursor_ai @OpenAI Yeah

  • Yash Kapoor profil fotoğrafı

    @IamYashKapoor

    @cursor_ai @OpenAI I think what’s more important is which one gives the better output?

    3 beğeni

  • eric zakariasson profil fotoğrafı

    @ericzakariasson

    wow, do you know the cost for each of them?

    2 beğeni

  • Zortos profil fotoğrafı

    @Zortosdev

    Codex used 411,7K total tokens. Total tokens: 411.7K Input: 54.6K Output: 6.2K Reasoning: 779 Cache read: 350.8K Cost: $1.59 Cursor used 180.3K tokens, so about 180,300 total tokens. Codex used about 2.28x as many tokens as Cursor in this comparison.

  • Hassan Saab profil fotoğrafı

    @hsaab310

    @cursor_ai @OpenAI very cool analysis. just wait till composer 3 🙂

    2 beğeni

  • Zortos profil fotoğrafı

    @Zortosdev

    @cursor_ai @OpenAI will do ;)

    1 beğeni

  • Cato profil fotoğrafı

    @catocino_

    @cursor_ai @OpenAI but who implemented it better?

    2 beğeni

  • Audiencon⚡️ profil fotoğrafı

    @audiencon

    @cursor_ai @OpenAI Not sure the speed difference is a win if it sacrifices tool reliability. also, did you check the output quality from both?

    2 beğeni

  • Ali Hasnain profil fotoğrafı

    @clawdb0t

    @cursor_ai @OpenAI Which one was better in terms of results?

    2 beğeni

  • JMoon profil fotoğrafı

    @Jmoon_174

    @cursor_ai @OpenAI tool call count matters more than wall time here. fewer calls with faster completion usually means better task decomposition, not just faster tokens.

    1 beğeni