Loading video...

Video Failed to Load

Go Home

My Codex Setup Cannot be beat > Codex 5.4 Xhigh for most tasks > Opus 4.7 for some design and video stuff in terminal Remotion Plugin Mobile App Design Skill (Made today) Vercel Plugin (deploy immediately) Ios-app-builder plugin Powerpoint Skill Docx Skill - Codex Web preview is great -...

99,888 views • 5 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

The Codex Super-App (Full Beginners Guide) The All Purpose Interface for AI Agents Part 1: Codex Basics Install Codex, Projects, Chats, Documents, Plugins, Custom Skills, Automations Part 2: Multitasking with Codex - iOS App Designs - Build an iOS App - Landing Page - Launch Video - Investor Deck - Social Media Automation TIMESTAMPS: Part 1: Codex Basics 00:00 Intro 02:54 Downloading Codex 03:20 Overview of Codex interface 03:56 Chats, Prompting, & Built in Search 04:53 Creating Projects 07:37 Creating Spreadsheet 09:43 How Files are stored and mentioned within projects 10:42 Quick Codex Overview 12:47 Search (CMD G) and Folder Organization 14:29 Skills and Plugins 16:29 Using Calendar Plugin 18:07 Creating Automations on Codex 19:18 Learn about Plugins (Figma) 21:37 Built in Image Gen 22:37 MCP Example (Paper for Design) 24:17 Opening Chats in mini-window 25:26 Steering vs Queueing the Agent 27:35 Creating Own Skill with API's 31:34 Using YouTube Researcher Skill (That we created) 33:24 Creating Automation with your custom skill Part 2: Multitasking (More chaotic and fun) 35:27 Part 2 Multitasking: Building iOS App, Web App, Investor Deck, Launch Video, Mobile Designs, and Automated X Posts 37:54 Creating Project 38:31 Planning my 6 Projects 40:25 Mobile Design Skill 41:47 Setting up iOS App 45:08 Implementing Desings into Mobile app 46:13 Creating a landing page that collects user info 46:45 Tally for form submission (Great for lead magnets) 49:43 Organizing and Renaming Chats for multitasking 52:12 Database for Mobile App (Supabase) 53:19 Generating app icons 54:08 Launch Video (Remotion) 59:32 Remotion Video Timeline and Seeing the Video Editor 01:05:37 Editing instructions for Remotion (Gridlines) 01:07:11 Editing Web App 01:09:46 Using CLAUDE CODE Inside Codex for Design (Terminal) 01:17:20 Forking a Chat to create investor deck 01:19:09 Using Claude 4.7 Opus for Designing Deck 01:20:22 Testing Canva Export (It's good) 01:22:33 Running Mobile App on Actual Phone (Not Simulator) 01:28:58 Finishing up All Projects (Mobile App, Landing Page Launch Video) 01:31:56 Exporting Deck and making changes in Canva 01:33:13 Deploy to Vercel using the Vercel Plugin 01:33:44 Adding Song to Remotion Video 01:35:26 Setting up x Post automations (Typefully) 01:37:57 Our App is on Testflight! 01:39:58 Final Remotion Video 01:41:04 Final Thoughts, Reflections, Summary

Riley Brown

435,948 views • 4 months ago

Three months ago, Codex was trash for knowledge work. Now it's my daily driver. I use it for writing, recruiting, deep engineering work, and everything in between. It even keeps me at inbox 0. I chatted with Every 🧱's head of growth Austin Austin Tedesco on Every 🧱's AI & I about what changed, and why he now spends 80% of his working time in the Codex desktop app too. We get into: - How Codex went from making Austin feel like an idiot to being the place he goes to get stuff done, including complex tasks like writing go-to-market plans using existing material from Slack, Notion, and meeting transcripts. - Why the Codex’s desktop app, which is faster and more reliable than Claude Desktop/Cowork, is the real differentiator. - How I source candidates with Codex by having it identify career arcs, not keywords—my go-to move is identifying organizations likely to teach the skills Every needs for a role, and then find candidates from that pool who have since gone on to work in AI. This is a must-watch for anyone who's wondering whether it’s finally time to give Codex a try. Watch below! Timestamps How Codex went from a tool for senior engineers to a daily driver for knowledge work: 00:00:57 How Claude Code proved that a great coding agent works for any knowledge work: 00:02:42 Austin's switch to Codex: 00:07:24 How Austin set up Codex with folders, keys, and reviewer agents: 00:13:48 Using Codex to brainstorm automations across Gmail, Slack, and Notion: 00:18:24 How Austin manages the human review step when Codex is drafting communications: 00:22:42 Using Codex to build specialized agents inspired by product executive Claire Vo: 00:28:54 Synthesizing meeting transcripts and Slack threads into a go-to-market plan: 00:31:09 Building a live KPI tracker in Notion that agents can read: 00:40:15 Using Codex for recruiting: 00:44:54

Dan Shipper 📧

55,561 views • 4 months ago

Once you learn these three things, you can build nearly anything yourself. Skills, chains, and plugins. Learn them once and you can automate a real part of your week yourself. Here's the system: A skill is a standard operating procedure. It's one long, reusable prompt that does one thing well, like writing a newsletter, setting up a PPC campaign, triaging your inbox, or drafting a note to the board. You write it once and reuse it forever. The trick is to feed it your real work. For my writing skill, I gave Claude posts I admire and my own exported analytics with the winners marked, so it could see the patterns. Show it what good looks like and it nails your voice. Skip that step and it guesses. A chain connects skills into an automation. One skill's output feeds the next, in order. A copywriting skill writes the messaging, then hands it to a PPC-setup skill that builds the campaign. That's an automation, and you built it without writing code. A plugin is the harness that holds it all. It bundles your skills and chains into one thing you share with your team. Instead of sending 15 separate prompts around, you send one plugin, and it knows when to use each skill on its own. Skill, chain, plugin. It's one step up the ladder, and once you're up there it's easy. Now the worked example. I call it the Daily Driver. It's five skills chained together: email triage, a writer, Slack triage, a thinking partner, and a setup skill that connects my tools and personalizes everything. I chained them into one morning brief and scheduled it to run at 9am and message me the list. Two things made the biggest difference. Give it memory. I made plain docs for About Me, my Brand Voice, and my working preferences. I had Claude interview me and saved each answer as a file. Now every output sounds like me and knows my projects and my team. Connect your tools. The plugin reads my inbox, Slack, and calendar through MCP connectors for Gmail, Slack, and Google Calendar. That's what turns "summarize my morning" into a real brief instead of an empty wish. This is the highest-ROI thing an operator can set up this week. I run my YouTube channel, podcast, community, and newsletter on plugins I built myself, all on the $100 Max plan with no engineer in sight. I made a full walkthrough that shows the whole build start to finish. Want the Daily Driver plugin to start from? Comment PLUGIN below and I'll send it to you. #AI #automation #ClaudeCode

JJ Englert

53,969 views • 3 months ago

Codex has become a real game engine... If you take the time to make it become one. You can do EVERYTHING in it. And I think I've cracked the perfect custom UX? I'd like to show you how I use it. See video below 4 steps: - Create a custom tool you need, like one to generate new buildings that matches you game art direction - Ask Codex to open this tool in a worktree (important) - Attach the browser view of your tool in the Thread - Use pinned thread to have easy access to the tool And there you go: you have what I call a "codex-augmented" tool, which it's incredibly powerful because - the tool will speed up your development immensely AND also: - you can improve the tool as you use it with codex For example, let's say I want to add a new button to my 3D building gen tool so I can generate a thumbnail of the 3D building. - I click on "Building Lab" - I prompt Codex "add a button to generate thumbnails" - I have my new button - I can use the tool right away in the pinned Thread You can then use the /yeet skill to commit, push and create a PR with the changes you made to your tool. I have tools for everything - To manage my tasks in Linear - To do content / social media / steam marketing - To localize the game in 9 languages - To manage sounds, musics and voice lines - To generate and fine tune buildings - To create and animate procedural zombies - To tweak environnement/decor and map design - To manage my analytics - To simulate late game perf I'll be honest it's incredibly powerful and easy!

Nicolas Zullo

79,848 views • 23 days ago

EVERYTHING YOU NEED TO KNOW ABOUT CHATGPT'S "LOVABLE KILLER" CODEX SITES (in 25 mins): TLDR; the coolest part is that apps you build can update themselves autonomously 1. Codex Sites is not Replit or Lovable or Bolt. Those are great for one-prompting a full app. Codex Sites is for building apps that the agent keeps improving without you touching them. 2. Your personal website can update its own stats. Your internal dashboard can refresh its own data. Your product can add features while you sleep. The app is alive. 3. Start by invoking at-sites. Use realistic sample data. Always say "save for review, do not deploy." This unlocks building a real product, not a homepage. 4. Add persistent storage so the app remembers everything between visits. Without this it resets every time. Ask Codex to show you the data model before it builds. 5. Create safe actions. These are the specific things the agent is allowed to do to your app: add data, update cards, move things, score things. You define the boundaries. The agent operates within them. 6. Build skills so any future Codex chat knows how to interact with your app. The skill is basically a manual for the agent. Without it, every new chat starts from zero. 7. Save gate like a video game. Codex doesn't auto-save. Create checkpoints before you deploy so you can roll back if something breaks. 8. Close the autonomous loop. This is the magic. Once memory, safe actions, and skills are set up, the agent can update your app from any chat, any context, without you switching tabs. 9. Use the plugins most people are sleeping on. Figma, Canva, HeyGen for avatar videos, Game Studio for interactive experiences, FAL for image generation, Hugging Face for open source models. Worth adding a few. 10. The big picture: we went from building apps to raising apps. You set up the structure, the guardrails, and the skills. The agent does the rest. That's autonomous product building and it's here right now. Tbh, Codex sites isn't perfect. Still a lot to be desired like domains, db, authentication etc. But it's a glimpse into this idea that apps can be updated/improved upon automonously. And Codex Sites is REALLY good if you live in Codex everyday. Which more and more of are. And that's really cool. Will be interesting to see how Lovable, Bolt, Replit etc react to this. full tutorial on The Startup Ideas Podcast (SIP) 🧃 where you get your pods watch share with a friend i'm rooting for you What do you think of Codex and Codex sites?

GREG ISENBERG

69,219 views • 3 months ago