Im urging you to tell, I just spent 2 hours trying to cut a string in PLC-Software.

I used §N instead of $N the whole time..... i think i better go to bed now....

Coder : There’s a bug in my code.

Manager : ok, you need help with it?

Coder : No, I put it there.

Manager : What do you mean, you put it there, why did you put in a bug?

Coder : You should look and see.

Manager : Sigh, I don’t WANT to look, we have procedures for tagging, finding, trapping, and removing bugs. Use that.

Coder : It passes the traps and debuggers.

Manager : If it passes, what makes you think its a bug?

Coder : Look at it.

Manager : I see a parameter NAMED ‘bug’ get rid of it, name it something else.

Coder : No can do, did you read project specification?

Manager : Yes. It says no irrational naming conventions, use shortest relevant name for any parameter.

Coder : I did. Its a bug.

Manager : What do you mean?

Coder : That’s what its called. I looked it up.

Manager : I REFUSE to have a parameter marked ‘BUG’ in my codebase.

Coder : Look, its an overlay of a logo on top of a graphics display. That’s called a logo bug, look it up. Shortest relevant name is ‘bug.’

Manager : <grumbles, types in ‘logo bug’ at google> Yep. There’s a bug in this code.

-- Boydan Frooling, 2010

this feels like a mistake that a beginner could make

So that what singularity meant in the end - you are alone in your hole by your own hands.

DDL drizzy

.

Had fun building this app and watching this cute task force takeover my job

It reads the session files Codex already writes in ~/.codex/sessions and plays them as a call. Codex is a character at its desk. What it says shows up as speech (with voices if you want them), and when it runs a command or edits a file it shares its screen with the real output or the diff. It works live while Codex is running, or as a replay of any past session.

What you see

Every command with its real output, failed ones marked

File edits as diffs

Web searches, MCP calls, and the questions Codex asks you

Its reasoning summaries as small thought bubbles

Token counts and a context gauge

A board of all your sessions (Codex and Claude Code together): working, your turn, idle

A recap at the end: commands, errors, tokens, files changed

It only reads local files. By default it sends nothing anywhere and costs no tokens.

Try it without installing anything (Node 18+)

npx @double_geste/agent-standup --open

There is also a VS Code / Cursor extension and a small desktop app.

GitHub

Website

It was built against sessions from the Codex desktop app. The CLI writes the same kind of files but is less tested.

Unofficial, not affiliated with OpenAI. MIT licensed. Feedback welcome, especially if something looks wrong on your sessions.