Loading video...

Video Failed to Load

Go Home

new codex app first impressions! - pros: reliably coding in swift 🤍, a nice UI for kicking off concurrent threads/alerts, clearly there is a lot to unpack across automations/skills - asks: would love to see more killer use cases for automations, perhaps broken down by product type (iOS, web,...

13,440 views • 4 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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,128 views • 1 month ago

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 views • 1 year ago

I've been spending more time with Bezi to see how far I can push vibe coding a game on the Unity Editor. So far, I'm pretty happy with what I can achieve with Bezi. Here are some learnings: - Even though I use Bezi to do all agentic coding, I still have to perform a few small manual tasks in the Unity Editor - As a result, I feel like I am getting a hang of Unity's complex and clunky UI, which actually feels good! - This is one of those examples where Vibe Coding is a great way to learn game dev. - For big features, I can't state the importance of asking the agent to create a plan first before implementing the feature. It can work wonders. Most of the bigger features/ssytems starts with a clear plan. - The biggest strength about working with Unity Engine is the Unity Asset Store, there's so much good stuff in there, 3D assets, shaders, vfx etc that can really spice up your game, that other game enginers will need to build from scratch. - Because Unity Assets Stores sell UI assets packs, I was able to implement decent looking UI fairly quickly. For those of you that vibe code games, you know how much of a pain it is to implement UI. - I did meet a few hiccups along the way where Bezi seems to struggle a little with implementing some features, but usually with some retries it works out at the end, though it burns a ton of tokens. After spending more time with Bezi, I'm still feeling good about using it. I am able to get this PvZ style autobattler working in a few days!

Danny Limanseta

13,319 views • 2 months ago