{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69ab3b7c7036d739021982df/6a1a68badd90858af94b0b48?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"How I AI: My Weekly Codex Experiments","description":"<p>For deeper playbooks and analysis: <a href=\"https://natesnewsletter.substack.com/\" rel=\"noopener noreferrer\" target=\"_blank\">https://natesnewsletter.substack.com/</a></p><p>What's really happening when AI stops being a chat box and starts becoming a working context system?</p><p>The common story is that better prompting is about clever wording — but the reality is that the work is moving toward cleaner context, better task shape, and agents that can stay oriented through long runs.</p><p>In this video, I share the inside scoop on how I'm using AI this week: assembling context windows, using Codex on local files, and shifting from prompt engineering into collaborative task definition.</p><p>Why local folders can become clean context windows How Codex changes long document, spreadsheet, and code workflows What changed in prompting after agentic workflows got better Where Claude still fits for polish, salience, and design Why multi-threaded drafting now feels practical</p><p>For operators, builders, marketers, and executives, the important shift is not just which model wins. It's learning how to structure the work so the model can help you think, execute, review, and iterate.</p><p>Subscribe for daily AI strategy and news.</p><p>Hosted on Acast. See acast.com/privacy for more information.</p>","author_name":"Nate B. Jones"}