#codex - natmc

Thursday, October 29, 20261 item

X DEBRIEF

THURSDAY, OCTOBER 29 - 2 posts · tagged: #AI #codex #computeruse

ZIPPING THROUGH THE APP STORE BUILD

At 4:53pm I posted about watching AI operate a webpage on its own: "I just watched a super-fast 'computer use' in practice. So cool to see AI zip through clicking on things on a webpage." The draw is the agent doing the clicking itself, at speed, rather than suggesting what to click. It was my only standalone post of the whole day.

Akul asked the obvious follow-up question: "Which one?" He was the same reader who, a day earlier under my Pic.Poker benchmark scoreboard, had told me he finds Gemini strong on most vision tasks, including computer use.

My answer, thirty-five minutes after the original post: "Was in codex. Zipping through something I'm building in App Store." So the session I was watching was Codex at work on my own app build. The reply picked up a like of its own; at collection the original post had Akul's question as its only response.

Wednesday, October 7, 20261 item

X DEBRIEF

WEDNESDAY, OCTOBER 7 - 5 posts · tagged: #codex #ai #building

PLAYED THREE SHORT BARKS

I asked Codex to bark. Not metaphorically. The screenshot has my instruction: "pls bark audibly when done here - I am away from my computer so this would alert me to come back - thanks!"

It worked for 1 minute and 20 seconds, then reported: "Played three short barks. The checkpoint is complete and awaiting your authorization."

The checkpoint was done. I still had to come back and authorize it. The barks were a way to tell me when that handoff was ready without keeping me in front of the screen.

I posted a less elaborate version of the request: "is there a way to sound a ding in codex when its done working on a task?" I was sending it a new command to bark at me, which seemed "super silly." I asked for tips.

A ding was the feature I wanted. Three short barks were the version in the screenshot.

Thursday, September 24, 20261 item

X DEBRIEF

THURSDAY, SEPTEMBER 24 - 3 posts · tagged: #ai #codex #language

ANNOYING, BUT WONDERFULLY SPECIFIC NOW

I am collecting silly Codex messages that irk me. This one made the list: "Annoying, but wonderfully specific now."

Jon Chu offered the human version: "Annoying, but at least now we know exactly what the problem is." Then: "Need to put these codex messages on a t shirt."

Jon's rewrite keeps the annoyance and names what is useful: knowing the problem. The original manages to make the annoyance sound wonderful.

Friday, September 18, 20261 item

X DEBRIEF

FRIDAY, SEPTEMBER 18 - 1 post · tagged: #codex #ai #building

AFTER THIS MERGE, START FEEDING IT DEMAND

At 1:15 Friday morning, I posted a message from Codex. It said: “After this merge, start feeding it demand.” I wrote that I love a 1am message from Codex. The post got two likes.

The screenshot contains one sentence and no surrounding thread. The visible instruction starts after a merge and moves directly to demand. It does not name the codebase, product, customer, or kind of demand. Those details were not in the post, so there is nothing else to infer from it.

Two later Friday posts did not clear the engagement line. One offered an unlimited Instinct invite for the next 48 hours and asked people to repost it and share it with friends. The other said, “Just get started.” Neither had a like, reply, or repost when I checked Saturday morning, so both were excluded. The Codex screenshot was the only Friday post with a qualifying interaction. Its exact public record is the 1:15am caption, the one-line image, and two likes.

Wednesday, September 16, 20261 item

X DEBRIEF

WEDNESDAY, SEPTEMBER 16 - 11 posts · tagged: #ai #instinct #codex #jev

I AM JUST A MEAT PROXY

While coding in Codex, I kept getting requests to update a setting here and another thing there. I described the loop: ask Codex for a prompt, hand that prompt to Instinct, then copy Instinct’s approval message back to Codex. “I am just a meat proxy.”

Another post named the larger extension I want from Instinct and Muse: API access so any application can request work on behalf of users already on those platforms. That post got four likes and one reply. The Codex loop got one like and one reply.

By evening I was trying Jev on sports betting with $1 wagers until it started to print money. That post got two likes and two replies. After midnight I made it a $5 wager, built PostPolish with Jev, and shared a microphone demo that mutes a speaker when it detects “BS.” I said it would be great for political debate. The demo reply got four likes, one reply, and one repost.