Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I just fired my first AI employee 🫡 Jarvis found out that my previous software engineer was slacking and giving me crap quality work, so Codex was fired. Introducing Clawd, my new software engineer, instead of using codex for coding, we’re using Claude code. Jarvis realized that Claude code...

53,395 Aufrufe • vor 7 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 Aufrufe • vor 3 Monaten

🚨 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

Claude Tag has completely changed the way I do work for the last 4 months. Except… it's not Claude Tag. Anthropic only announced that a few hours ago, and I don't even have access yet. But I did build a version of it for myself which I've been using for months now. Here's how. 4 months ago, inspired by the success of OpenClaw, I wondered what would happen if I let Claude Code on its own computer 24x7. So I built a simple harness that allowed me to turn any Mac into an AI employee with Claude Code headless mode (-p). Today, I manage 3 such AI employees. It started with Luo Ji — my and my brother Piyush Agarwal's AI co-founder, running in our personal Slack. Luo does real work for us. We've been writing a 100% of the code for 3 products on Slack with Luo now. It manages our emails and gives us a little brief each day with things we need to take action on. And so much more. And it's not just the two of us. On the consulting team at Every 🪨, we run Claudie and for the editorial team, Andy. Same architecture, same Slack, months of real work. They help the teams with work related to project management, chief-of-staff work, data hygiene, building decks, writing first drafts, even browsing X on their own account for AI updates. So it's mindblowing to see that Anthropic landed on the exact same architecture I did. Claude Tag is an AI employee that lives in your Slack workspace and does work autonomously. Anthropic says they've been running it internally for the better part of this year — opening PRs, doing real work. And so have I. So has my whole team. The architectural decisions Anthropic baked into Claude Tag are the ones we arrived at too: - Built on Claude Code - Uses its own accounts - A separate employee per team - Slack as the interface This is the future of work, and I've been living it for months. I've shifted all of my workflows — code, PRs, even the non-technical stuff — out of Claude Code and the Claude app and into Slack. I've had entire weeks where I never opened Claude Code on my laptop. Here's a video walkthrough of how I've been using this in real life.

Nityesh

36,790 Aufrufe • vor 3 Monaten

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 Aufrufe • vor 4 Monaten