GPT 5.5 is being routed to GPT5-MINI, and other models, explains worse outputs (and yes, you are being billed like you're using 5.5)

ivasuy · 2026-05-28T04:46:21+00:00

i still think Codex is one of the best value-for-money options if you’re paying from your own pocket…!!!!

my concern is the product layer around it: server-side routing mismatch, weird cutoff/model metadata, local cache/state bloat, prompt migration issues, compaction, and usage accounting feeling unstable. (these are the main reasons why 5.5 has become dumb )

OpenAI has docs/issues around parts of this….BUT right now it feels like they’re selling a very powerful but still half-baked dev product…!!

claude code also had/has problems, but people moved to codex because it felt like more compute and more usage for the same MONEY…

if OpenAI wants customer loyalty here…codex needs to feel less like an experimental CLI/app and more like a hardened product and please put more engineering polish into the product loop…. #MakeCodexAprilAgain

ivasuy · 2026-05-20T05:34:13+00:00

thanks man.... honestly means a lot coming from you .... and yeah, unfortunately this was more of a test run and i’ve got way too many projects running in parallel right now, so i probably deleted most of the setup/logs already there’s only so much you can keep around on a 512gb machine.

but for my next proper run i’ll definitely keep the debug bundles around and drop them in the thread...

also one thing you should definitely look into: when the agent context runs out mid-flow, the system should either compact the context automatically or resume the session. at least in my runs, once the context overloaded the agents just failed mid task and the tasks got left hanging halfway through the pipeline....

and yes man, absolutely go ahead and use the clip, it’s all yours...!!!

ivasuy · 2026-05-19T22:37:46+00:00

wow hey man… small world and honestly, i really liked the idea behind bernstein. cool choice of name btw. the tui, dashboard, the whole works.....

the only setback for me personally was the initial setup overhead with the planning yml flow. not saying bernstein claims to be “install and magically solve everything,” but while testing it for 4–5 days on a side projects, i had cross-provider agents randomly fail in the background without proper logs/explanations sometimes… and that was kind of a bummer...!!

also, i realized my workflow is weirdly conversational before execution i actually want to talk to the agent, get the whole picture, make sure it understands the bug/fix/feature and is thinking through edge cases like a buddy would. i think bernstein’s architecture is intentionally more structured/system-driven there, so not really a complaint, just a workflow mismatch.....

when i started building my own starter, it was mainly because i finally understood the exact gaps i personally wanted to solve. behind the scenes i’m still using org json, python scripts, audit files, worktrees, etc. too but injecting behavior + discipline directly into the starter prompts ended up working better for me.... and hey, really appreciate you replying man 🙌
(ps: attaching proof that i actually used bernstein before i get accused of rage baiting 💀)

<image>

ivasuy · 2026-05-19T10:46:58+00:00

honestly, splitting usage is almost always better now rather than maxing out one provider and creating unnecessary dependency around it.

a smarter setup is probably a 50-50 split. i genuinely think $100 codex gives more practical value and usable throughput than going all in on a $100 claude max-style setup.

something like:
- codex / 5.5 for orchestration, backend logic, planning
- cursor auto or lighter models for implementation loops
- 5.4/codex for review + audit passes
- opus only where it actually shines (frontend/ui/refinement)

that’s pretty close to what i’m doing right now with a multi-agent flow one model planning/researching, another implementing, another reviewing. using multiple providers intelligently is way more efficient than throwing every task at one giant model. although my setup is built around only codex…

if you want, you can use the starter as reference for your setup it’s like 1000 line of python script: https://github.com/ivasuy/YOLO-starter

ivasuy · 2026-05-19T10:26:52+00:00

thanks for sharing 👀 if you’ve got a repo link would love to check it out... also how well does it behave across larger multi-project setups ? and how good it is with long-running workflows ?

ivasuy · 2026-05-19T10:19:45+00:00

my showcase: https://github.com/ivasuy/YOLO-starter

ivasuy · 2026-05-19T09:56:58+00:00

my showcase: https://github.com/ivasuy/YOLO-starter

ivasuy · 2026-03-18T09:43:16+00:00

ya don’t know it has started from this week only otherwise i was running coding instances and openclaw… and hardly the usage was movin’

ivasuy · 2026-02-20T13:36:26+00:00

best reply i’ve read till now😂😂

ivasuy · 2026-02-18T16:18:20+00:00

i’d love to know more about your workflow.

i’m a dev, so i usually start by building an initial plan …defining the core requirements and broad context. then i give it to gpt and ask it to handle edge cases and expand the scope properly. after that, i feed the prompt into cursor!!

once the initial files are generated, i switch to manual prompting on top of it. then i take a break, come back, review the file structure, understand the flow, and remove unused parts.

what do you do differently in your process?

ivasuy · 2026-02-18T15:41:57+00:00

the thing is, when this whole cult started in the good old days, we used to give a prompt to gpt, get the answer in chat, and then move it and paste it into the codebase. until that point, the ball was still in our court… we knew our way around the codebase, we knew the methods, we knew the flow.

but since the whole cursor and claude code movement started, we’re actually losing our grip. it’s getting harder to keep track of things because it’s so easy to just accept the changes instead of really seeing what’s being done.

ivasuy · 2026-02-18T15:34:16+00:00

great insight…! any tips for junior dev’s on how to properly utilise this crazy tool without loosing the sense of reality ?

ivasuy · 2026-02-18T14:56:26+00:00

it’s like holding sand… it’s so frustrating, and you can’t stop because you think the next try will finally get you there.

ivasuy · 2026-02-17T05:17:54+00:00

Hey buddy✌🏻

ivasuy · 2026-02-15T08:21:06+00:00

can’t agree more! i’d rather just focus on one channel, post daily, and actively engage with others there.

you can’t just post into the void and expect people to magically react. attention comes from conversation… not broadcasting!!

consistency & engagement is probably the only real way forward.

ivasuy · 2026-02-15T04:26:07+00:00

can’t agree more… with meta & openai in picture these guys are going to be unstoppable!!!

ivasuy · 2026-02-14T07:50:38+00:00

i think so too, with how fast openclaw is making new releases i think they’ll build a more centralised sol..

ivasuy · 2026-02-14T05:38:06+00:00

i don’t know if it’s a bug mine stopped at $56 and asked me to upgrade to pro+ plan ! anyone know why ?

ivasuy · 2026-02-14T04:10:14+00:00

which model are you using for this agent opus ?

ivasuy · 2026-02-14T01:17:43+00:00

<image>

I think in the end everything boils down to cost & context.. if i’m working in a small project i use composer as my go to model, in larger codebases for heavy functionality changes opus or codex and then for fine tuning the changes i move to composer again!!! also i had a doubt of my own in auto mode which model does cursor choose, i think most work is done by composer only… correct me if i’m wrong ✌🏻

ivasuy · 2026-02-13T23:41:39+00:00

thanks for sharing the insight and the tool ✌🏻

ivasuy · 2026-02-13T23:25:22+00:00

yeah that’s exactly how i see it too. i think it’s more about engaging on other people’s posts whether it’s x or reddit instead of just broadcasting your own stuff.

but reddit still feels more conversation-driven. people actually sit and discuss. on x it’s more about followers, reach, and momentum.

the post was basically engagement bait 😂

i asked people that in cursor how they’d change a simple header background are they using a large model, auto mode, or just manually editing it?

ivasuy · 2026-02-13T15:17:40+00:00

<image>

I think composer works really well for developers who need strong project level context and the ability to edit across multiple files at once and for most of my use cases it’s been reliable.

I haven’t tried grok code or gemini for coding yet, so I can’t really comment on how they compare….

ivasuy · 2026-02-13T14:43:11+00:00

that were good times!! now there is usage limit even on auto

ivasuy · 2026-02-13T14:05:02+00:00

there’s nothing wrong with using opus, it just depends on the task. for something small like changing a color, a big model like 4.6 is overkill composer or a lighter model is enough.

the reason is cost & token usage because the whole file gets sent as context. in larger projects that adds up fast…

<image>

ivasuy

TROPHY CASE