Loading video...

Video Failed to Load

Go Home

I used my codex reset to cut this OpenAI Dev Day recap, where I cover my favorite releases for the day (spoiler alert: I'm now an expensive Ultrafast girl) What I cover: (00:58) Dots: early impressions and rough edges (06:57) Spaces: working with humans and agents (10:37) Sites, connectors,...

11,651 views • 3 days ago •via X (Twitter)

9 Comments

Dassi AI's profile picture
Dassi AI3 days ago

@OpenAI Ultrafast fixes decision latency, but state verification across internal tools is the real production moat.

cris pérez de lope's profile picture
cris pérez de lope3 days ago

@OpenAI Great update claire, thank you!

Spencer Schneidenbach 🦈🇺🇸's profile picture
Spencer Schneidenbach 🦈🇺🇸3 days ago

@OpenAI Devday was a vibe!!

Hillary Bush's profile picture
Hillary Bush2 days ago

@OpenAI sponsored by how do it know

Lee Wyatt Corp's profile picture
Lee Wyatt Corp3 days ago

@OpenAI Free Codex reset, spent on the recap. Priorities in order.

Rohan's profile picture
Rohan3 days ago

@OpenAI Which of the rough edges in Dots would hit a team before a solo user?

Rivaldo A.'s profile picture
Rivaldo A.3 days ago

@OpenAI expensive Ultrafast girl? hope the Wi-Fi bills match the speed.

Ash Designs's profile picture
Ash Designs3 days ago

@OpenAI The Dots rough edges part is the one I want. Always on agents need a totally different UI than chat. What felt most off on day one, notifications or knowing what it's doing in the background?

John K's profile picture
John K3 days ago

@OpenAI Dots with the rough edges called out, then Spaces — that pacing makes the Dev Day pile feel watchable.

Related Videos

Codex tip: once GPT-6.1 Sol is your main model, stop running Astra on every turn put Astra on call as an architect agent GPT-6.1 Sol keeps writing the code Astra only gets spawned at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Astra reviews. Sol ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big models only see the ones that split - the full tree > GPT-6.1 Sol on high runs the main session > explorer reads the code on Luna > worker edits and runs tests on Sol > researcher pulls the docs on Luna > all three on medium > Astra on call as the architect > auto_review checks every approval paste the tree and this prompt into Codex ↓ "Rebuild my Codex setup around this tree: 1. Check ~/.codex/agents and .codex/agents for agents that already fit explorer, worker and researcher. > Draft new TOML files only for missing roles > explorer and researcher on gpt-6-luna, worker on gpt-6.1-sol, all with model_reasoning_effort medium > Add an architect agent on gpt-6-astra, model_reasoning_effort high, whose only job is reviewing plans, repeated errors and finished work > Skip any that pin a different model and list them 2. In ~/.codex/config.toml set model to gpt-6.1-sol, model_reasoning_effort to high and approvals_reviewer to auto_review 3. Find anything that would override this (active profiles, flags in my shell aliases, agents.default_subagent_model). Report it, change nothing 4. Add one rule to AGENTS.md: spawn the architect before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

delost

918,253 views • 2 days ago

I feel burned out having to manage context for my agents/harnesses/runtimes. And what "grinds my gears" is the fact that Astra will burn through my usage simply due to loading a plethora of skills. I spent time to make sure the previous models like Sol are able to meet my production bar... As of today, it feels like I have to throw that out or manage that between two model types. I thought we had AI to help us with this? Shouldn't this be the job of the model provider especially if I use their harness? But Ray, you just have to...(do new undocumented thing) and it'll just work. BRUHHHHHH you drop models/updates every few weeks and keep changing this. Now repeat for the last 6 months... Cursor Projects just dropped their beta and I'm starting to see where the puck is going with a workflow like this. I can design what happens from PRs, bug fixes, testing, and the entire SW Dev lifecycle without living in a terminal or managing skill files. This is going to save me lots of time as my project evolves and I don't have to spend much time maintaining skill files or handing off things between agents. I can switch models and ship software like a professional. Here is my first look at Cursor Projects and I'm very bullish on where this is going. Timestamps 00:00 This Thing Called Projects 00:44 Grok Bot Went Crazy Viral 01:53 Grok Bot Forgets Sometimes 02:55 The Project Page 04:10 Agents, PRs, and Listening 06:02 The Exec Status Board 08:41 Files That Live on the Cursor Side 10:35 The Same Chat on My Phone 11:26 Still in Beta, Cloud First

Ray Fernando

42,108 views • 20 days ago

In this livestream I break down the OpenClaw AI agent narrative from the operator’s perspective: what it actually is, why it’s different from ChatGPT/Grok/Claude Code, and why “it’s just automation” misses the real shift. We cover the practical unlocks (local execution, persistent memory, computer-use + browser control, reusable skills/plugins) and why this design pattern can replace a lot of expensive SaaS workflows over time. Then I zoom out to the crypto angle: why the market will mint endless OpenClaw “slop” coins, how I think about separating infra from hype, and the two names I’m watching (BNKR + CLAWD). 00:00 Why the OpenClaw AI agent narrative is bigger than you think 00:39 Two-part video: OpenClaw productivity first, crypto narrative second 01:30 What OpenClaw is (an AI agent framework, not a chatbot) 01:44 Why ChatGPT, Grok, and Claude Code are still useful but incomplete 03:19 OpenClaw vs n8n and Zapier for automation 05:03 Why Zapier pricing breaks real businesses 06:07 Why running locally matters (any app, any chat platform) 07:56 Persistent memory: how agents learn your style over time 09:55 Computer-use agents: browser control and no-API workflows 11:27 Skills and plugins: reusable workflows that self-improve 13:52 The simple setup and why model choice is flexible 16:05 Cross-platform ops: Telegram, Slack, Discord, and email in one brain 20:52 Why AI SaaS tools get replaced by agent-built workflows 25:37 What this is not: no AGI, no “sentient” coin story 29:55 How to approach the OpenClaw coin wave (infra over slop) 32:43 BNKR and CLAWD: my two picks for exposure to the narrative

VirtualBacon

22,428 views • 7 months ago