How to Use /Goal to Do More With AI

Today on the AI Daily Brief, a primer in using the slash goals primitive in codex and cloud code and how to use it to level up your use of AI. The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI. Alright, friends. Quick announcements before we dive in. First of all, thank you to today's sponsors, robots and pencils, section, super intelligent, and blitzy. To get an ad free version of the show, go to patreon.com/aidailybrief, or you can subscribe at Apple Podcasts. And if you wanna learn more about sponsoring the show, send us a note at sponsors@aidailybrief.ai. Today, we're talking about something that a lot of power users of AI are incredibly excited about, which is slash goals. So let's dive in. Today, we are doing another very operator centric episode. Recently, I did a show about codex maxing, effectively a set of tips and best practices on how to get the most out of OpenAI's codex. Now in many ways, while that episode was specific to codex itself, a lot of the interaction patterns, you could also follow in other harnesses like Claude Code. The Codex Maxing piece was built off of a blog post by OpenAI's Jason Lou. Jason wrote up about nine techniques or interaction patterns that he had discovered allowed him to get the most out of codex, not just for coding, but for other types of knowledge work as well. And some of those tips represented fairly different types of patterns. One of them, for example, is the idea of durable threads or monothreads, where instead of using some sort of infrastructure like a project, where you have multiple threads all related to the same topic that share a memory base, you instead use a single thread relying on the harness's compaction tool to make sure it always preserves the relevant context. You also saw in that codex maxing post a number of ideas about how to effectively reduce the latency between the human providing guidance to the model and the model getting things done. I think in some ways, in fact, that you could kinda summarize the overarching direction of what Jason was exploring as a way to move past the turn based paradigm of AI, in other words, the standard way of interacting with chatbots that we've all gotten used to over the last few years where you give it a prompt, wait for it to do a thing, review the thing it did, develop and provide it your feedback, and wait again for the next thing that it does. By using features of codecs like the side panel where you can inspect artifacts as they're being built, voice input to more freeform give feedback with a lot of additional context because you're talking through it, steering to insert that feedback even as codex is still working, and some other features like remote control and heartbeats to make sure that this …