Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Calling on Codex Fans! I need your help 🫵 I'm introducing Codex Marketplace, a community collection of plugins, skills, and hooks curated by YOU. Yes, you! Help me make this the best resource for everyone who wants to build incredible software with Codex. Getting started is simple, submit your... show more

am.will

27,007 subscribers

41,319 просмотров • 2 месяцев назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Introducing... The Base Skills Repo 📙🔧 Power your Claude, Codex, OpenClaw with skills to build on Base I show in this video how I one shot a Base Pay demo in one simple prompt with the Base Account skill Use it now: npx skills add base/skills

Introducing... The Base Skills Repo 📙🔧 Power your Claude, Codex, OpenClaw with skills to build on Base I show in this video how I one shot a Base Pay demo in one simple prompt with the Base Account skill Use it now: npx skills add base/skills

Youssef

56,202 просмотров • 4 месяцев назад

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

67,388 просмотров • 28 дней назад

It’s Codex Thursday, and yes, we have updates for you. First up: Appshots, a new way to bring the context of what you’re working on into Codex. On your Mac, press Command-Command to attach your app window to a Codex thread. Codex gets both a screenshot and text from the window, including content beyond what’s visible onscreen. Appshots are available across plans on Mac, with enterprise access coming soon.

It’s Codex Thursday, and yes, we have updates for you. First up: Appshots, a new way to bring the context of what you’re working on into Codex. On your Mac, press Command-Command to attach your app window to a Codex thread. Codex gets both a screenshot and text from the window, including content beyond what’s visible onscreen. Appshots are available across plans on Mac, with enterprise access coming soon.

OpenAI Developers

1,863,543 просмотров • 1 месяц назад

Looking for a Codex meetup in your city? Our ambassador community is bringing Codex to you. Create and ship projects with your local developer community, compare workflows, grab coffee, and meet people building with Codex.

Looking for a Codex meetup in your city? Our ambassador community is bringing Codex to you. Create and ship projects with your local developer community, compare workflows, grab coffee, and meet people building with Codex.

OpenAI Developers

292,167 просмотров • 4 месяцев назад

CODEX SKILL TO BRUTALLY TEST ANY STARTUP IDEA! Most startup ideas sound good. This Codex skill tells you why they probably won’t work. Just give Codex your idea and it pressure-tests it for you -> finds the core assumption -> exposes fatal flaws -> checks if the problem is real -> maps real competitors -> plans your first 10 customers -> defines a 2 week MVP Install: npx --yes codex-startup-pressure-test-skill@latest 100% open source. Repo in bio

CODEX SKILL TO BRUTALLY TEST ANY STARTUP IDEA! Most startup ideas sound good. This Codex skill tells you why they probably won’t work. Just give Codex your idea and it pressure-tests it for you -> finds the core assumption -> exposes fatal flaws -> checks if the problem is real -> maps real competitors -> plans your first 10 customers -> defines a 2 week MVP Install: npx --yes codex-startup-pressure-test-skill@latest 100% open source. Repo in bio

Kappaemme

508,824 просмотров • 2 месяцев назад

Codex is unusable. I generated one image with GPT Image 2.0, gave it to Codex, and used one simple prompt: “Create me a web game from this image.” You give it a simple image like this, and suddenly you realize you can build: • a voxel map • an editor • tile animations • a playable browser prototype This is getting ridiculous.

Codex is unusable. I generated one image with GPT Image 2.0, gave it to Codex, and used one simple prompt: “Create me a web game from this image.” You give it a simple image like this, and suddenly you realize you can build: • a voxel map • an editor • tile animations • a playable browser prototype This is getting ridiculous.

Givros

83,052 просмотров • 1 месяц назад

Reminder: You can use Codex code review as part of your ChatGPT subscription 🙂 1. Head to 2. Connect your GitHub 3. Enable code review 4. Choose between review all PRs, just yours or trigger explicitly with "Codex magazine review this" To not spam you Codex will respond with 👍 unless it finds high priority items. You can use AGENTS.md to shape what a high priority item is.

Reminder: You can use Codex code review as part of your ChatGPT subscription 🙂 1. Head to 2. Connect your GitHub 3. Enable code review 4. Choose between review all PRs, just yours or trigger explicitly with "Codex magazine review this" To not spam you Codex will respond with 👍 unless it finds high priority items. You can use AGENTS.md to shape what a high priority item is.

dominik kundel

88,982 просмотров • 3 месяцев назад

Introducing Ferix - the skill issue killer. Ferix is built around Vercel's ‘npx skills’ command which Guillermo Rauch announced yesterday. Skills are stored in repositories on GitHub which means finding the skills you need for your project isn’t intuitive and you have to go searching. Ferix fixes this problem and acts as a central hub for all skill repositories. You an add a repository in 5 seconds and easily view it’s contents. So far I’ve added Better Auth, Expo & Vercel's agent skills but any user can add a supported repository. Let me know what you think and anything that can be improved! Autumn skills coming soon👀

Introducing Ferix - the skill issue killer. Ferix is built around Vercel's ‘npx skills’ command which Guillermo Rauch announced yesterday. Skills are stored in repositories on GitHub which means finding the skills you need for your project isn’t intuitive and you have to go searching. Ferix fixes this problem and acts as a central hub for all skill repositories. You an add a repository in 5 seconds and easily view it’s contents. So far I’ve added Better Auth, Expo & Vercel's agent skills but any user can add a supported repository. Let me know what you think and anything that can be improved! Autumn skills coming soon👀

Charlie Lamb

35,704 просмотров • 5 месяцев назад

How do you get GitHub Copilot to understand your entire codebase? Like this.👇 With one click, the Copilot coding agent can now analyze your repo and auto-generate custom instructions.

How do you get GitHub Copilot to understand your entire codebase? Like this.👇 With one click, the Copilot coding agent can now analyze your repo and auto-generate custom instructions.

GitHub

28,378 просмотров • 7 месяцев назад

With Alignerr, you can earn $30 to $50. This video is a step by step guide to help you get started and increase your chances of getting approved on Alignerr. Watch till the end and I’ll see you on the printing side.

With Alignerr, you can earn $30 to $50. This video is a step by step guide to help you get started and increase your chances of getting approved on Alignerr. Watch till the end and I’ll see you on the printing side.

FinegirlDami🧚🏾💜

47,816 просмотров • 2 месяцев назад

The OpenAI Codex repo turned into a Knowledge Graph! 🤩 If you want to start working on massive codebases and serious projects, you need to use CodeGPT’s Knowledge Graphs. Here’s a step-by-step 🧵 guide to create your Codex graph and connect it to VSCode 👇

The OpenAI Codex repo turned into a Knowledge Graph! 🤩 If you want to start working on massive codebases and serious projects, you need to use CodeGPT’s Knowledge Graphs. Here’s a step-by-step 🧵 guide to create your Codex graph and connect it to VSCode 👇

Daniel San

179,466 просмотров • 1 год назад

Write this down: If you choose to be part of a team… showing up as less than your best is selfish. Your standard impacts everyone else. When you don’t bring your best, you lower the ceiling for the whole room. Lead accordingly.

Write this down: If you choose to be part of a team… showing up as less than your best is selfish. Your standard impacts everyone else. When you don’t bring your best, you lower the ceiling for the whole room. Lead accordingly.

Alan Stein, Jr.

17,854 просмотров • 4 месяцев назад

OpenAI just shipped plugins for Codex, so now you can one-click add Box and your favorite coding assistant gets a cloud file system ☁️ Here's a demo of Codex fetching a product design document for an app I'm working on & building it for me from scratch in minutes ⚡️

OpenAI just shipped plugins for Codex, so now you can one-click add Box and your favorite coding assistant gets a cloud file system ☁️ Here's a demo of Codex fetching a product design document for an app I'm working on & building it for me from scratch in minutes ⚡️

Carter Rabasa

14,703 просмотров • 3 месяцев назад

we built the first sane way to debug your agent locally. you can see your traces. codex/claude code can too. this lets them write evals and test your agents automatically. best part: it's completely free and open source. install with 1 line. (github below)

we built the first sane way to debug your agent locally. you can see your traces. codex/claude code can too. this lets them write evals and test your agents automatically. best part: it's completely free and open source. install with 1 line. (github below)

ben hylak

193,440 просмотров • 1 месяц назад

Codex has come a long way since April. Over the next two weeks, we’re releasing a series of videos to help you get better acquainted with Codex — starting with how to use the Codex CLI with GPT-5-Codex.

Codex has come a long way since April. Over the next two weeks, we’re releasing a series of videos to help you get better acquainted with Codex — starting with how to use the Codex CLI with GPT-5-Codex.

OpenAI Developers

190,153 просмотров • 8 месяцев назад

I built a new plugin! You can now trigger Codex from Claude Code! Use the Codex plugin for Claude Code to delegate tasks to Codex or have Codex review your changes using your ChatGPT subscription. Start by installing the plugin:

I built a new plugin! You can now trigger Codex from Claude Code! Use the Codex plugin for Claude Code to delegate tasks to Codex or have Codex review your changes using your ChatGPT subscription. Start by installing the plugin:

dominik kundel @aiDotEngineer

1,284,335 просмотров • 3 месяцев назад

Codex with ChatGPT 5.5 is the best vibe coding tool on planet Earth right now It's the smartest model combined with the best app experience Whether you are a beginner or pro, this is the video you've been waiting for Here's how to build INCREDIBLE apps with Codex ChatGPT 5.5:

Codex with ChatGPT 5.5 is the best vibe coding tool on planet Earth right now It's the smartest model combined with the best app experience Whether you are a beginner or pro, this is the video you've been waiting for Here's how to build INCREDIBLE apps with Codex ChatGPT 5.5:

Alex Finn

42,113 просмотров • 2 месяцев назад

Starting today you can use Codex in Claude Code 👀 /plugin marketplace add openai/codex-plugin-cc Try it out today with: /codex:review for a normal read-only Codex review /codex:adversarial-review for a steerable challenge review /codex:rescue to let codex rescue your code Enjoy Codex-ing!

Starting today you can use Codex in Claude Code 👀 /plugin marketplace add openai/codex-plugin-cc Try it out today with: /codex:review for a normal read-only Codex review /codex:adversarial-review for a steerable challenge review /codex:rescue to let codex rescue your code Enjoy Codex-ing!

Vaibhav (VB) Srivastav

953,637 просмотров • 3 месяцев назад

yesterday, at the Codex hackathon, i ended up solving this problem by building an MCP connector app that turns ChatGPT into Codex, sort of. 1. you get to use GPT-5.5 Pro by exposing your local dev environment to ChatGPT, so you can use 5.5 pro for planning and handover to codex to execute it 2. you get to 2x your rate limits, just like last month, because apparently ChatGPT and Codex have separate rate limits here is the quick demo

yesterday, at the Codex hackathon, i ended up solving this problem by building an MCP connector app that turns ChatGPT into Codex, sort of. 1. you get to use GPT-5.5 Pro by exposing your local dev environment to ChatGPT, so you can use 5.5 pro for planning and handover to codex to execute it 2. you get to 2x your rate limits, just like last month, because apparently ChatGPT and Codex have separate rate limits here is the quick demo

waishnav

542,510 просмотров • 18 дней назад

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

JJ Englert

16,176 просмотров • 2 месяцев назад