Why We Switched From Claude Code to Codex

Codex is one of those things where three months ago, six months ago, it was trash. If anyone from OpenAI is on the call and listening to that, I stand by that a hundred percent. If you have a great general purpose coding agent on your computer, it's actually really great for any kind of knowledge work. If it can write software on its own, it can do any kind of knowledge work on its own. When I sign on during the day, Codex is the first thing I open. It is pulling in whatever I need from Gmail, Slack, Notion, Stripe, all of our data sources. It's where I spend like 80% of my time working, overwhelmingly because the app itself is just so good. There's a new operating system for how and where you're going to get your work done. And it's this kind of agent management interface. Hello, everybody. Welcome to Codex Camp, Codex for Knowledge Work. Psyched to have you, psyched to have you on this auspicious GPT 5.5 day after release day. Hope you're doing well. I'm here with our head of growth, Austin. Austin, say hello. Hello. We're psyched to have you. We are psyched to do this. Codex is one of those things where, you know, three months ago, six months ago, it was trash. And if anyone from OpenAI is on the call and listening to that, I stand by that a hundred percent. And it was really built for senior engineers doing pair programming. So it would argue with you to make you feel stupid. It was just, it was like a little autistic. Like it didn't have any emotional intelligence. And I think OpenAI had this interesting strategy or this interesting theory starting with GPT-5 that your vibe coding was going to happen in ChatGPT and that was where all that stuff was going to live. And then senior engineers are going to use Codex to like do all of their programming work, but we're going to hobble the model so it doesn't do anything bad. It's in a sandbox, all that kind of stuff. And I think basically what happened is Anthropic figured out that having a model that's pretty usable and fast and smart and also emotionally intelligent on your computer that can access your computer is a really, really great experience for programmers. And it means you could throw away a lot of the old stuff that you used to have in a programming environment where it was built for typing code. You could just type commands into your terminal and then it would start working. And then I think what Anthropic figured out is if you have a great coding agent on your computer, it's actually really great for any kind of knowledge work. If it can write software on its own, it can do any kind of knowledge work on its own. And we started to move from this world where programmers had been delegating their tasks, starting to delegate their tasks inside of cloud code, to now any kind of knowledge work is being delegated inside of cloud code and cloud co-work and all that kind of stuff. And I think OpenAI, they had this original split. It's like, oh, you're going to do all your vibe coding in ChatGPT. And I think they saw what was starting to happen with cloud code. And over the last maybe three months or so, they have done this hard pivot on Codex where it has gone from a senior engineer only tool that is really for pair programming to, I think, like, it is my daily driver for this kind of work. I use Codex for everything from deep engineering stuff to writing to recruiting. I do a lot of, I actually do a fair amount of recruiting. It's really good for that. And I'll give you some use cases later. But they sort of figured out that having this general purpose agent on your computer with the ability to write code, the ability to access your file system, the ability to have a browser, and wrapping it in a desktop app is like the ideal next step for knowledge work. And I think that they built the best current version of that. And what it is starting to snap into focus now is that there's a new operating system for how and where surface for how and where you're going to get your work done. And it's this kind of agent management interface. And that's whether or not you're using cloud code or cloud co-work in the desktop app or Codex in the desktop app. It's becoming this race between the model companies where every each model company has their own surface like this for agent management and desktop app for agent management. That's at its core, a programming agent that's used for knowledge work. Anthropic has cloud code and cloud co-work. OpenAI has Codex. XAI recently essentially bought Cursor. And Google is the only one that, I mean, they have anti-gravity, but I don't think no one is seriously using it for that yet. But I imagine Google will do this too. And that's the race. That is the race that's happening. And so I think for us who gets, who get all the benefits of being able to use these tools, it's really important to be, be bouncing around between these. So like use it, for example, using Codex so that you can feel what it's like to work in an agent first world. Because once you add, once you add an agent that is like the, your primary way of accessing and using software and the internet and all that kind of stuff, it opens up all this interesting stuff that wasn't possible before because you can send your agent out to go talk to other pieces of software and come back. And, you know, we can get into more of the details there, but I want to get into like the more of the concrete use cases, but that's the world that we're starting to live in. You are doing work on your computer through codex or co-work and, and your agent is your interface to a lot of the work that you're doing and a lot of the, a lot of the software that you use and a lot of the stuff that you do every day. And that's actually really fun. It's really cool. There's a lot of good stuff here. And so I wanted to, I wanted to bring Austin in to, to help do this because Austin is our head of growth. And I think he had his real agent pill moment. You tell me, Austin, but probably like three or four months ago. And the agent pill moment was really cloud code. And I sort of remember you just being like, oh yeah, on a, on a Monday morning being like, oh yeah, I just was on my computer all weekend. Like I, I was like 12 hours a day. I didn't go out or anything because I was using cloud code. And you started to use it for all those, all the kind of knowledge work tasks that a growth marketer would. And over the last couple of weeks, as we've been using 5.5 and I've been telling you for a little bit, you should try codex. It seems like you've, you've actually just shifted everything over to codex and 5.5. And so I think you're a great person to talk about, you know, sort of what you're seeing and how, and how that is how this has changed, how these agent management interfaces have changed your workflow. And then why you like codex. And then I would love to get into some demos of your actual codex workflows so that we can sort of see things from your perspective. Yeah, that sounds great. So I, yes, my like agent pilled moment was spending a week going deep into cloud code in the CLI, probably in like December into January, hooking it up to everything I do for work and for my personal life and finding that I, I use Warp as my like CLI interface. And finding that the things that could automate the things that could handle for me and then the way it could work as a thought partner to make my work better. It was like, this is the only way I want to do the kind of knowledge work that requires strategic thinking and data analysis and shipping marketing copy, like a bunch of stuff that can get you spread out across a bunch of apps and tools during the day. And in maybe in February, you kept nudging me to be like, you really should try codex. There were things you liked about it. And if someone says that at every, if anyone on the team says that, like, I'll go try it. And I like to push myself and play around with more engineering-y tasks, especially to see what these models are capable of. And so I tried to build a personal vibe-coded app in codex because that was one of the things that you said that it was really good for. And my immediate response was like, I think it is better at building the app, but I can't tell because it's nothing has ever made me feel more stupid than Codex like two months ago. Like I always, I use compound, our compound engineering plugin that Kieran Klassen made for basically everything, including knowledge work, but especially if I'm trying to build an app or ship a PR to the, to the site. So I made a plan in the plan. It comes up with like three questions and for like which direction we should go. And I had no idea what the hell it was talking about. It was like, do you do one of any of these three? And every question I was like, please explain this to me in more detail. And its response was basically like, why? Like, why don't you just do what I'm recommending? And I found a way to, I basically stayed in codex for all engineering stuff because I did like the results, even if I didn't love working in it, but I would say 80% of what I was reaching for was, was cloud code in the CLI. And when we got our hands on the new GPT model a month ago, the, the, the first thing I felt was at the very least, there's parity between I was talking to our editor-in-chief, Kate, yesterday to show her like how I would recommend getting started in Codex. And this is my recommended prompt. I am happy to put it in the chat for people. We can put it in the email as well. And so all I did was, I'm putting in the prompts here. I only have posted panelist access, so I'll send it later or something. Okay, yeah, maybe read it out. You can all agree that housing is expensive. Rent or mortgage, doesn't matter what you're paying, it stings every month. But Built can make it feel a little better. Built started out by rewarding members for their rent. Now, as of 2026, Built members can also earn points on mortgage payments wherever they live. Every housing payment earns points you can use toward flights with top travel partners like United and Hyatt, Lyft rides, Amazon.com purchases, and so much more. This is actually pretty cool, and I have some friends that use this and like it a lot. Something that's underrated is that Built members also get access to a neighborhood concierge. They can make restaurant reservations, book fitness classes, and find new local spots, all while still rewarding you at 45,000 merchant partners. It's like having a personal assistant baked into where you live. It's simple. Being a renter and now owning a home is better with Built. Make sure to use our URL so they know we sent you. And now, back to the episode. Yeah, yeah. Okay, I can zoom in as well, I think. There we go. So through the plugin tool with Codex, I went in and did the manual clicks to connect all of the tools I use every day, like Gmail, Slack, Notion. And then I went to a new chat inside of this folder that was built through CloudCode. CloudCode built this whole every growth OS system. There's a CloudMD file in there. And it's saved locally. It's also synced and pushed to GitHub. And so I just opened that project inside of Codex when I started working here. And I start a compound engineering brainstorm workflow because it is, again, just kind of like a thing I reach for of let's think about this thing together, me and the model. And basically what I said is like, go take a look at the things I use the most, which are Notion, Slack, and Gmail, and think of some automations that would help me with my work. I find that when I'm trying something new, whether it's a model or an app, having an agent, having a very smart frontier model, tell me how to use it, tell me what it should do is exactly where I want to start rather than thinking of it myself. And I usually start here. Sometimes I will describe a very specific problem, but this is very helpful for me and I think a good generic prompt for people to start with. And Codex comes back. It looks at what's going on for me and for the company right now. And I thought these were really good that like, it has this kind of follow-up radar. This is a big thing that happens with people who do knowledge work, who do partnerships, who do social media marketing, that there's all this stuff coming at you across a bunch of different sources. Like, what if it handled the triage for you? What if it had this kind of like command center when we run a camp or an event, which usually requires a bunch of moving pieces and moving parts. Like Dan mentioned for recruiting and hiring, we don't use a tool like Ashby or something. We kind of have it all synced through Notion because apps like this and agents can kind of like handle a lot of the pipeline and tracking work for us. And you can just ask it to automate it for you. And so it does that and it asks me like, which ones look good? What do you want to tweak? For the sake of this demo, I didn't give it any real feedback. I was like, looks good. And this is actually the thing I've always been most impressed with Codex for and for the models is that it's like, great, I made this automation for you. And I do find that they just work incredibly well. They require very little tweaking to be like, this is a thing I would and do use every day. There's this set of instructions that it comes up with based on what it knows about me. I can change when it runs. I can give it additional insights. I can connect it to other things, but mostly it just works. There's one that works for me that just at the end of each day now compiles all of the stuff that I haven't responded to yet, drafts the replies, and we can kind of like knock it out together of what to say or like, actually, all I need to do is just give like a thumbs up Slack reaction to something and it'll do that for me. It's kind of like a dumb agent. Like I think of agents like this as like the dumb ones that just do the right thing every time. And then the smart ones like an open claw or a plus one, the products we have coming that's like, you'll work back and forth with it and like have a more of like a creative strategic partner. And Codex is good at building both. And I can show kind of like the smart agent set up, but if someone is looking to be like, can I see what this thing can do to help me with knowledge work? I would start here in like a brainstorming automation state because it is. And I think you'll also be surprised by how fast it is. And you'll be like, oh, I'm starting to get what this thing could do. This is so sick. Your Codex usage is far surpassing mine in terms of interestingness. I'm getting a lot of ideas. I wanna just actually pause here. Normally we take questions at the end, but I think it would be kind of interesting. If you have a question about what Austin has just showed, it would be nice to let people come up and just ask a question or two just to see what the vibe of the room is like. So please raise your hand if you have a question and we will call on you. Margaret, welcome. Please introduce yourself and ask your question. Hi, can you hear me? I'm Margaret. I'm in Plymouth. And my question is, what is your review step look like? So it's saying, don't send, post archive, or modify without explicit approval. So what does that look like? Is that like, do you call up, say, hey, let's do the review flow now? Or does it doing push notifications to your phone or what? Thanks. Yeah, so for this, what I prefer, and I was actually talking to a friend at dinner last night who said they did the same thing on their own. They came up with this too, is like everything. I work primarily in Codex. I do all the drafting and setup in Codex. And then it's helpful for my brain to have the final review step actually live in the external app. So it will draft all the Slack messages, and then I can go to Slack where Slack has that like draft reply tab, and I can go and knock them out. And I do find that it like freshens up my brain a bit to be like, here's where I'll just make sure that this is what I want to send to a human being. Same thing for email. It like creates all of these drafts in Gmail. And I'll actually go open Gmail and look at them and knock them out. I know some other people who just have it actually come up inside of Codex, and they're like, yeah, sure, send it. It looks good there. I do the same thing for strategic planning. It pushes to either a proof doc, the like agent-friendly markdown file that Dan made, or a Notion doc. I use them for some different things. And I just like for like the last pass before humans engage with it to step away from this agentic space and have a final check in another surface. That's really the only time that I'm like leaving the app to do something. That's brilliant, thank you. Sweet, all right, we'll do one more and then we'll keep going. Alex, please introduce yourself and ask your question. Hi, my name is Alex. I'm a musician and I do a lot of gigs and get emails from clients all the time. So I have to sort my leads from, you know, my newsletters and all that informational stuff. So how do you make sure that you prompt Codex to keep those emails safe for me, the ones that, you know, that require a personalized response? And I just wanna make sure that, you know, I don't send something that, you know, loses me money or something. Yeah, so for me personally, I rely a lot on Cora, the internal, like the app that Kieran runs at Every for like the AI email assistant that's a part of the Every subscription. It's really helpful now that inside of Cora, there is a like a CLI and API connector that I can work in Codex and tell it, tell Cora, which is managing my email filtering and my email rules, what I want and what I value. The way I do that is the same thing I would recommend whether you use Cora or not, which is you have the agent interview you to get an understanding of what the rules should be. I always find that I get a better result rather than saying what I think the rules should be. And so I'll do a brain dump using monologue, our speech-to-text app saying, here's the problem I'm facing. My email's a mess. Let's figure out how to triage it. I think it would work perfectly well if you wanted to try starting it as an automation in Codex or a rule in Codex of saying like, I think these are the things I wanna make to just ship a proof doc and I can see how close you are. And one thing that it doesn't really do super well unless I tell it to, and I want to install this as like a workflow is that it doesn't go read our calendar of upcoming posts and launches. And so as it was going, I was like, oh, you always forget this. This is the message I'm sending of like, actually look at everything that's scheduled because I have to account for that and go-to-market plan. And then it makes a plan as a proof doc. I went and looked at it and I was like, again, I maybe have five minutes in between meetings and I'm like, this is really good. Like you kind of have every, you have the architecture enough that I want you to like factor in one other change, and then just ship the plan to Notion. And the plan it shipped to Notion, I was reading it and I was like, this is basically 80 to 90% of the way there. And that's not because I'm relying on the model to come up with our go-to-market strategy. It's that I'm relying on the model to look at all of the things that we've already said and thought about the go-to-market strategy, piece it together, and then review it, right? Come with what will work, with what's not. There's a lot of important context loading that happens here where like, it knows what our target ICP is. It knows what our goals are. It knows how we think about narrative positioning. And before this was possible, the only thing I could have done was either block off a whole day to sit and do this or get done with my work for the day at like six or seven and then stay up all night writing this. And this has been such a game changer for me. And the other part of it that I think I've found is really helpful is that I don't make this plan for humans. I make this plan for humans and agents. And primarily for humans to understand through agents. And so when I sent it to the team working on the go-to-market, they can't read it. And it's like digestible to humans. But the thing that it's really helpful for is like, it's the full plan sectioned off all in one. And so Brandon, our COO, who's like deep in this product, can ask his plus one, can ask codex, can ask code, like, let me know what Austin's plan is. Like, summarize it for me. Let me know the business case. Brandon has to come up with the pricing modeling for the plan so he can work with an agent against the plan. And as someone who spent so much time in my career thinking about like literally how the proposal or go-to-market document looks like, how is it going to look when I present to the CEO, like this two-page plan for like a budget I'm asking for. Like, is it going to make sense to their eyes and like really fine-tuning stuff? Giving up on that and just saying like, is the plan really good and is it going to make sense to like Dan's agents if he approves it? To me, it makes me work faster. It makes the work better. It means that I don't have to think about all this like kind of dumb stuff that doesn't matter. That like, it's to me a much more like powerful and fun way to work. I totally, totally agree with that. You said so many things that are interesting there. The first one is just normalize sending agent documents around. And that's why we have proof. It's just such an easy way to send the markdown documents that we generate to each other and interview them together. And it's like there, I think there's this whole strand of AI stuff that's like, make AI write in your voice. We even do this with Spiral, but there's this other strand of just like normalize AI writing because I would actually prefer to read your agent's writing than your writing in a lot of cases because I know that it's just easier for you to get all that, that thinking together in a format I can read if you, if you have your agent write it. The thing I care about is, do you stand by it? Have you thought about it? And if I talk to you about it, will it be clear that if I talk about a particular bullet point in it, like you've thought that through. And as long as we have the trust that that's going to be the case, then I absolutely prefer the, the agent version. In the future, humans face a new problem. What do you do when your computer is doing your work for you? One answer, take a cloud walk, an idea by Every. Every, the only subscription you need to stay at the edge of AI. Totally. Like my friend Rachel Carden who runs the, the great like substack newsletter, Linkin.bio about social media had, had a really good piece this week about frustrations for people working in social for like every, like this pressure they feel that everything has to run through AI and the quality going down. And one reason why is that there's that dichotomy of like, what do you actually stand behind? Like, are you running something through AI and you like, you know, maybe your manager did it and they don't even know what it, what it said. And the thing I love about working at Every is like, you, you show up to a meeting, you, you've like shared an AI written document ahead of time. And the expectation is that you're going to stand behind all of it, that someone will ask a question of what's in that document and you, if you say like, oh, I didn't even know that was in there, it's like you're, you're, you're exposed, right? But the other nice thing is that we continue to keep investing in skills and workflows and tools to kind of ensure that never happens. Like I have rules inside of this project file to be like, if don't, don't add anything that I haven't like said in another context. I want your suggestions. Send your suggestions to me in the chat, but don't put it in a, in a document. And like, depending on how big the context gets, these models can follow or not follow those rules, which is another reason why I always leave codex for that final review before it goes to the like humans I work with. Yeah. And I think that that last thing that, that, that I want to point out that you said is like, a lot of the time that you spend working is about taking thinking you've already done and putting it into a form that other people can read and consume. And the important part is doing the thinking. There, there is something obviously about like, I love writing. Writing is a good way of thinking. And sometimes you actually want to do the writing yourself because you want to think about it for certain types of things and certain types of people. But there's a lot of stuff like company strategy where a lot of the thinking happens out loud in meetings. And there's also times, like, for example, I'm writing something that's sort of like a, it's like a retrospective on the last three and a half years of AI and like where I think we're going. And that's so hard to sit down and write, but it's much easier to just like dictate. So I just took a monologue note where I was just like saying stuff and it, I'm using the AI to help me like figure out what I'm really trying to say. And in those cases, I think it's just so nice to record stuff, give codex access to everything, and then just have it spit out a strategy doc and go through it to make sure it, it's stuff you agree with, but it's such a time saver. And especially if you're someone who like Austin or like me, like you're in meetings a lot and so you don't necessarily have huge chunks of time in your day to like go do a big strategy document because you're just trying to stay on top of whatever is happening. It helps you do that in the cracks of your day and do a lot of that thinking. And I just, I love it for that. Yeah, me too. I want to show one more thing before we get into more questions, because like, I want to show kind of like a, a more like mix of knowledge work and engineering-y stuff that like would never have been possible without these kinds of tools. And that I really love codex for, which is I've been rebuilding our KPI tracker every week. I'll just like show it here for a bit. So, um, we have so many different parts of our business at uh at Every. And uh it's very difficult to get all of those um data points in one source of truth in a traditional tool, like even PostHog, which I really like and a lot of our data runs through it. To get one dashboard that is, again, both human and, human and agent facing that is up to date with all of the metrics we care about. I, I haven't found a great solution for just like, you know, going to PostHog and having it, having it do it. So, um, I've been rebuilding our KPI sheets inside of Notion with the goal in mind of any, anyone can point their agent to look at it and see how are new paid subscription trials doing? How are page views doing? How is uh Monologue iOS MRR doing all versus plan, all of this stuff. Because one, it helps you work as a human, but it also really helps you automate agentic work so that you can say like, if your agent sees that we're tracking behind on SEO for a keyword we should be winning on, it can go just like ship a bunch of landing pages for us to try to win more on it if the, if the source of truths are good. And so I have been doing this big kind of like, to me, complex uh workflow problem in codex of let's build this sheet together how to get something for existing users and send it out as soon as we can. Cool. All right, let's do some questions. Rich, please ask your question. So I saw at the beginning you were using compound engineering as kind of part of your workflow. Are you using kind of like the off-the-shelf plugin or is there tweaks to it and kind of where does that work and maybe not work when you're outside of the, you know, kind of code creation workflow? So I find that there's no overwhelming need to fork your own version of compound engineering. I used it for a long time for all of my knowledge work and it was extremely powerful for me. And then maybe about two months ago, the main thing I noticed was reading the agent's response to, especially the review stage of watching the reviewers that Kieran and Trevin had built that are very specific to engineering. I was like, oh, this like, the thing you'll see the agents do is say like, I'm supposed to go through this review step. It looks like it's designed for engineering. It's thinking about security and front-end design when this is a go-to-market plan. The agent will then like change the path. The agent will be like, I'm going to review this for something else rather than reviewing it for security. And so the thing that I did was I went and forked a version of it that is actually publicly available on our GitHub called Compound Knowledge, which is built exclusively for me taking the compound engineering plugin, which is also public and you can go fork and going inside of, I think I started in cloud code. Now I updated it, updated in codex and saying like, I want to tweak this to general knowledge work. And this is the thing I was referencing around the like reviewers being much more specific to knowledge work around like strategic alignment and data accuracy. I think more than anything, this is like a really fun way to learn and a fun way to like kind of like push yourself on using models. You're welcome just to go use this one. We'll include it in the follow-up email to the camp. But I think it's a cool, like I learned a ton just by doing this. I had never made like a plugin like this before. And to make your own version of say you do like social media marketing and you want to make sure all the reviews go through your style guide, your like past performance. I got a ton out of operating this way. If you just want the compound engineering to make your work better, it absolutely works really, really well for knowledge work just kind of out of the box. Got it. Yeah. No, interesting, particularly using kind of all the, the end of step pieces like compound that that's still apparently a valuable step for you. Yeah. The compound step is really valuable. We have inside of our notion, a go to database of after you're done with a session, you can send the learnings from the session to actually a team wide shared compound source of truth. Whenever I'm done with any session in codex or cloud code, the agents are instructed to ask me, should we compound this, save it somewhere for the learning? And should we turn any workflow from this session into a skill so that we can just do it automatically each time. Got it. Cool. No, I'll check that out. Thanks. Cool. All right, Rory, please introduce yourself and ask your question. Hi, my name is Rory and I'm in your head. And is there, are there anything about the way you work at every like maybe taking some time after meetings, like ending them a few minutes early so that you can do those things that you'd recommend to teams that are adopting workflows like yours? Is that clear? Yeah, I think so. Like, um, to say it back to you, like what I'm hearing, which is like a very real challenge here is that, um, It's that it's so exciting and tempting and alluring to like spend a lot of your day playing with stuff. Also spend a lot of your day continuing to push on, like, if I just get this automation right or this tool right, my work is going to be like a hundred times better and easier. And I actually find myself a lot, like on a lot of days spending most of my time, not in meetings, trying to build really good tools and automations that work well and not making the time to do the actual like tasks that have to push the business forward. Like, like, uh, shipping the social posts for the day or, or whatever. And I, I don't really have like an awesome answer for it, outside of the fact that like the, the playing around one is like kind of core to how we operate at Every. It's, it's a thing that Dan like pushes all of us to do. It's one reason why I love working here. It's also like, to me, the best way to learn and, and makes me better at everything I do. And then, um, the, the, the only kind of like guidance I've given myself is that like these automations in codex keep me on track to get the work done so that when I'm too deep in, um, in like playing around and building this, like, uh, there's like a social automation tool I'm working on that I've been like deep in for a while. Um, the codex automations make it so that I like, you know, make sure Brandon gets what he needs for this, like, um, some like biz dev plan where we're doing. I do find myself over-indexing on learning and, and playing because of how exciting and powerful the models have been and that more I have to pull, like continue to pull myself into the, the like required day-to-day tasks and the, the urgent stuff that's happening. Yeah. And I, I also sort of read your question, Rory, and you tell me if this is wrong, but as like, how do we do more of the AI stuff, the more of the playing, even to even get started on this stuff in our day-to-day, uh, if we're like busy all the time and I, and what are the organizational practices that we have for that? And yeah, I just think, like Austin said, like, it's just like a culture. It's a cultural thing. Um, we just love playing around and that's like, that's part of our job. Um, and I think there's this, There's this thing happening right now where the tools and the workflows are changing so fast that just focusing on how your job currently works, you can run as fast as possible. And someone using a new tool with a new paradigm and a new workflow is just going to beat you by default. And so if you just give yourself some time to play around, it may feel like a waste of time, but you're leveling yourself up to a different game at a different level. And I think that's really important. And some of the organizational practices that we have to help people do that are really around. So one of the things we do twice a year is called think week. Um, and we just literally don't do any of our day-to-day work and we just spend a week together, just like playing around with new stuff and building stuff and learning and, and being together. And you don't necessarily have to do a whole week of that, but, um, I think it's really good to maybe do that once a quarter for a day or something like that. Um, and just give people the time and space to, if, if you can. Sweet. Um, all right, y'all. So that is our program for today. Thank you for coming. Uh, we love seeing you. We love doing this with you. Remember every is the only subscription you need to stay at the edge of AI. We would love it if today you would go tell one of your friends to go subscribe to every. Um, we want to get more people in here. We just think we're, we're right at this amazing point in history where we get to surf, ride this big wave together and figure it out together, together. And, um, please, please tell your friends. See ya. Thanks y'all. Oh my gosh, folks, you absolutely positively have to smash that like button and subscribe to AI and I. Why? Because this show is the epitome of awesomeness. It's like finding a treasure chest in your backyard, but instead of gold, it's filled with pure unadulterated knowledge bombs about ChatGPT. Every episode is a rollercoaster of emotions, insights, and laughter that will leave you on the edge of your seat craving for more. It's not just a show. It's a journey into the future with Dan Schipper as the captain of the spaceship. So do yourself a favor, hit like, smash subscribe, and strap in for the ride of your life. And now, without any further ado, let me just say, Dan, I'm absolutely hopelessly in love with you.