Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Biggest lesson from OpenClaw is that a good teammate doesn't start from scratch everytime you check in. They remember what was decided, what's still open, and proactively help you. Today we launched heartbeats in Codex: automations that maintain context inside a single thread over time. Instead of each run...

119,157 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche 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,221 Aufrufe • vor 1 Monat

OpenAI member of product staff Alexander Embiricos describes the evolution of "Lord Bottleneck," an internal Codex loop developed by a single staff member that ultimately ended up creating a tight feedback and improvement loop for new user experiences: "This person on the growth team needed to figure out what experiments to run. And they needed to write code to run the experiment. Then they needed to analyze the experiment." "They started using Codex for each separate thing. So they had it run a bunch of analyses, interrogate the data, talk to Codex about the data. Then they would pick an experiment, and ask Codex to write the code. Then they would run the experiment, then ask Codex what the results of the experiment were. Then they would produce a deck." "All steps they were doing individually. They didn't start by saying, 'I'm going to automate this entire thing,' because that's hard and scary. They just started with using Codex to accelerate themselves." "Then, they started connecting all these things together into a giant skill. And one day, they just said [to Codex], 'Why don't you do this every morning?'" "They gave it a name: 'Lord Bottleneck.' Because it's solving the bottlenecks of friction for new users." "Now, every morning, Lord Bottleneck evaluates past experiments, looks at data, proposes some [new] experiments, and offers to the team to run the experiments. The team picks [what experiments to do]. Then Lord Bottleneck is like, 'Ok cool. Here's some code or whatever config that needs to be done,' runs the experiment, and they go and do the same loop the next day." "It's really serious value. I forget the numbers, but it's produced significant company value automatically through Codex."

TBPN

80,403 Aufrufe • vor 1 Monat

🚨 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 Aufrufe • vor 1 Jahr