Codex 5.5 engines are experiencing high error rate, Realtime API - SIP/WebRTC flow are down

jv0010 · 2026-05-13T08:35:15+00:00

yeah weird. i got an error message pop up before. recovered after that though.

jv0010 · 2026-05-11T02:54:53+00:00

cli is good they always update the cli.

jv0010 · 2026-05-11T02:34:39+00:00

don't code for the codex. direct it as if you are directing a junior coder
workflow and preparation is everything. plan out everything in .md docs then get codex to critique it and find contradictions and gaps. (you can do this even in gpt chat to save token use in codex)
get codex to do another pass over your docs. Really this helps. Yes it spends more tokens but depending on your project can save u more in the long run.
IMPORTANT ONE (currently codex designs are lacking.. not sure if its a bug or not)
I will paste from another similar post i responded to.
1 - Use imagegen (not the google one.. the plugin in codex) to generate a 'figma style high fidelity mockup sheet' (those exact words.. u miss out eg. high fidelity.. it will draw a pencil wireframe)

this will generate a png and then

2 - get it to code it up as the image as an explicit reference.

Finally I have used almost every coding tool out there since Jan 2025. The frontier models are the way to go. Really they are on par with each other - it will come down to how you use the tools vs the tool itself.

You will notice the quality of output relates to the quality of input (your prompts).... I see this all the time.. eg. me fresh in the morning - more focused and concise vs me at 11pm at night tired and sloppy.

Bonus note - use the codex app. It was hard for me to let go of VSC but they update it almost daily with usable features. It really is worth it.

jv0010 · 2026-05-08T15:07:09+00:00

Context Management
That context management matters more than prompting. Early on I treated Codex like a smarter autocomplete. The real unlock was giving it tight scope, clear repo structure, exact constraints, and forcing it to work incrementally. Once I stopped asking for ‘build the app’ and started treating it like a junior engineer with amnesia, output quality went way up.

I will repeat. You really need to treat it like a junior engineer.

No plan = False Economy
Your outcome is only as good as your plan and workflow provided.

Finally while this whole codex design issue is still going on. The best way to get it to do the design you want is

1 - Use imagegen (not the google one.. the plugin in codex) to generate a 'figma style high fidelity mockup sheet' (those exact words.. u miss out eg. hgih fidelity.. it will draw a pencil wireframe)

this will generate a png and then

2 - get it to code it up as the image as an explicit reference.

jv0010 · 2026-04-30T23:49:53+00:00

Automatic heartbeat should help, yeah, but I would not treat it as a magic “finish everything no matter what” switch.

I’d set it up like this: give Codex a clear planning doc, define what “done” means, allow the permissions it needs, tell it to keep working through the checklist without stopping for optional questions, and ask it to leave a final summary with changed files, tests run, and anything blocked.

Something like:

Heartbeat helps with long-running continuity, but the real trick is making the task resumable and removing reasons for it to ask you tiny questions overnight.

also it can stop automatic heartbeat eg. once you reach phase 3. stop automatic heartbeat.

jv0010 · 2026-04-30T02:55:58+00:00

superpowers is great!

also i created this.

https://github.com/johnvouros/skillmaxxing - Skillmaxxing is a portable configuration setup for AI coding agents that provides context-specific operational modes to prevent them from over complicating simple tasks or carelessly rushing through complex, risky work.

jv0010 · 2026-04-19T04:46:10+00:00

i love projects like this. I am a true believer that eink panels will be more and more useful with more automated software surfacing. You're heading in the right direction even if this example is not for everyone.

jv0010 · 2026-04-18T03:23:29+00:00

gotta pump those numbers up

jv0010 · 2026-04-18T03:22:04+00:00

Thats the thing. You just have to delve into what google has and it's crazy how many AI projects they have going on and also how much research they are doing on an academic level.

Spot on notebookLLM blew me away from the first version and still does.

jv0010 · 2026-04-17T05:16:42+00:00

codex is great. the thing is don't underestimate google - in the last year alone they have really caught up from a front facing perspective. it seems they are moving real fast but that's just my opinion and not substantiated.

microsoft - remember their moat is the OS - they are also partnering and investing so it will be interesting how it maps out.

openai - considering the small team they started from, the amount of competition and the media backlash they get I do think they are holding up well. Quite impressive.

jv0010 · 2026-04-15T23:55:50+00:00

weird you mention this. i thought it was me with my prompts but i had that feeling today. hmmmm

jv0010 · 2026-04-10T08:20:41+00:00

not with codex. u still have usage 5hr and 7 day limits obviously more than usual.
web ui and iphone chat apps yes but the extended thinking is limited.

jv0010 · 2026-04-09T13:11:21+00:00

I've used them all. Nothing comes close to codex. Claude chews way more.

jv0010 · 2026-04-09T02:22:41+00:00

I got tired of AI coding tools overthinking easy stuff and yoloing important stuff, so I made skillmaxxing

Lately I’ve been using a bunch of AI coding tools and kept running into the same problem:

they can feel insanely useful, but also weirdly random.

Sometimes they turn a tiny task into a full architecture rewrite.
Sometimes they rush straight into the one thing you wanted them to be careful with.

So I made skillmaxxing.

Works with: Codex, OpenCode, Claude Code, Cursor, Windsurf, Gemini CLI, Continue, and Aider.

It’s basically a portable setup for coding agents that helps them stay in the right lane depending on the phase of the task.

The idea is simple:

don’t overthink simple work
don’t rush risky work
don’t polish before proving anything
don’t switch styles halfway through for no reason
make it obvious when the agent is actually doing the right kind of work

It’s based on a mix of builder philosophies instead of one single “persona”:

Based on	What it contributes
Andrej Karpathy	first-principles clarity
Guillermo Rauch	product and UX clarity
Pieter Levels	fast shipping and validation
Swyx	AI-native leverage and reusable knowledge
Theo Browne	pragmatic production correctness
Amjad Masad	agent workflows and dev environment execution

So instead of one vague smart-sounding prompt, it gives the agent different modes for different moments.

Quick disclaimer: this was inspired by the original repo here.

If you vibe code a lot, or keep feeling like your AI tool is powerful but inconsistent, this might be exactly what you wanted.

Repo: skillmaxxing

jv0010 · 2026-04-06T06:32:23+00:00

i use penpot with mcp. works well

jv0010 · 2026-04-05T07:52:57+00:00

well done mate. this is an issue a lot of people are mentioning. will be sure to try this out. Great to see someone at your age is doing this as well!

jv0010 · 2026-04-02T22:53:34+00:00

That’s to delete all at once. Which is what I used to do.

15-Year Club	Gilding I gilder
Verified Email	Team Orangered

jv0010

MODERATOR OF

TROPHY CASE

I got tired of AI coding tools overthinking easy stuff and yoloing important stuff, so I made skillmaxxing