正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Most engineering processes were built for teams shipping 10 to 15 PRs a month. Kun Chen, ex-Meta L8 engineer, is now shipping 40+ PRs a day with agents. That breaks a lot of existing processes behind: → Code review & QA → Merge gates and team handoffs When output... show more

Peter Yang

243,426 subscribers

15,566 次观看 • 2 个月前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Former Meta top-tier engineer: "I don't review the code anymore. I got to a point where I never catch anything the agents don't catch." He runs 20-30 agents at once and ships 20-40 PRs a day, work that used to take a full team a month. In 55 minutes he explains everything he knows and builds a fully working workflow from scratch. Watch it, then read the full guide on building loops below.

Former Meta top-tier engineer: "I don't review the code anymore. I got to a point where I never catch anything the agents don't catch." He runs 20-30 agents at once and ships 20-40 PRs a day, work that used to take a full team a month. In 55 minutes he explains everything he knows and builds a fully working workflow from scratch. Watch it, then read the full guide on building loops below.

Anatoli Kopadze

184,731 次观看 • 1 个月前

Engineering teams require focus now more than ever. We’ve changed the way we solve for paper cuts in the product while maintaining our speed of shipping: "The second [a bug] comes through Slack it triggers an agent that figures out the right team to send it to. That team’s custom agent will then do a first pass at a task on Claude. We’ll find similar customer feedback bugs if they exist and then tag an on call engineer where they just review a bunch of PRs” - Sarah Sachs

Engineering teams require focus now more than ever. We’ve changed the way we solve for paper cuts in the product while maintaining our speed of shipping: "The second [a bug] comes through Slack it triggers an agent that figures out the right team to send it to. That team’s custom agent will then do a first pass at a task on Claude. We’ll find similar customer feedback bugs if they exist and then tag an on call engineer where they just review a bunch of PRs” - Sarah Sachs

Notion Developers

15,009 次观看 • 1 个月前

Insane: 90-95% of Claude Code is now written by Claude Code. I asked Mike Krieger (Anthropic's CPO) what changes when so much of your code is written by AI? His answer: The bottleneck moves from coding/design to: 1. Upstream: aligning the team around what to build. 2. Downstream: the PR merge queue, reviewing and merging all of the new code into production. Anthropic is where other product teams will be in a year or two, so it's important we pay attention. "I would expect that a year from now, the way that we are conceiving of building and shipping software changes a lot. Because it's gonna be very painful to do it the current way."

Insane: 90-95% of Claude Code is now written by Claude Code. I asked Mike Krieger (Anthropic's CPO) what changes when so much of your code is written by AI? His answer: The bottleneck moves from coding/design to: 1. Upstream: aligning the team around what to build. 2. Downstream: the PR merge queue, reviewing and merging all of the new code into production. Anthropic is where other product teams will be in a year or two, so it's important we pay attention. "I would expect that a year from now, the way that we are conceiving of building and shipping software changes a lot. Because it's gonna be very painful to do it the current way."

Lenny Rachitsky

369,920 次观看 • 1 年前

Dumb loops beat clever workflows. A great talk about Ralph Loops. Build Dumb AI Loops That Ship by Chris Parsons. Most teams building with AI agents reach for multi-agent orchestration, planning graphs, and elaborate tool chains. Then they spend months debugging them. A single loop that processes one ticket at a time, evaluates its own output, and improves on the next run will outperform all of it.

Dumb loops beat clever workflows. A great talk about Ralph Loops. Build Dumb AI Loops That Ship by Chris Parsons. Most teams building with AI agents reach for multi-agent orchestration, planning graphs, and elaborate tool chains. Then they spend months debugging them. A single loop that processes one ticket at a time, evaluates its own output, and improves on the next run will outperform all of it.

𝗿𝗮𝗺𝗮𝗸𝗿𝘂𝘀𝗵𝗻𝗮— 𝗲/𝗮𝗰𝗰

23,908 次观看 • 2 个月前

Cursor pays engineers $1,100,000 a year to run teams of AI agents that ship code while they sleep. [The CEO of Cursor explained in 9 minutes how they ship at 100x speed using team of agents] ↓ Save this before everyone copies the playbook 1. Engineers no longer babysit one assistant. They manage dozens of agent colleagues working in parallel, each on its own remote machine 2. Validation contract before code, not after. Humans only at scoping and review. 3. The agent team handles the full loop : planning, coding, testing, shipping PRs with each agent specialised for a role. Watch the guide. Then read the guide below by Khairallah AL-Awady

Cursor pays engineers $1,100,000 a year to run teams of AI agents that ship code while they sleep. [The CEO of Cursor explained in 9 minutes how they ship at 100x speed using team of agents] ↓ Save this before everyone copies the playbook 1. Engineers no longer babysit one assistant. They manage dozens of agent colleagues working in parallel, each on its own remote machine 2. Validation contract before code, not after. Humans only at scoping and review. 3. The agent team handles the full loop : planning, coding, testing, shipping PRs with each agent specialised for a role. Watch the guide. Then read the guide below by Khairallah AL-Awady

Avid

636,555 次观看 • 3 个月前

placed 2nd, winning $3000 at Anthropic x Elevation Capital push to prod hackathon! ⚡️ > we built claude code but as a game > your entire repo becomes an isometric city > files are buildings with the height determined by the number of files > choose your crew for a task aka your model > visualise agents constructing buildings (files) in realtime > open PRs are ships. navigate to a new island to visualise PRs and review the changes > built using the Claude sdk > software engineering is shifting towards managing multiple agents rather than reading file diffs. we don't want you to scroll reels while your agents do work. shoutout to team Devfolio as always for the best hackathons. big shoutout to the team Fahim Arjun R ♥️

placed 2nd, winning $3000 at Anthropic x Elevation Capital push to prod hackathon! ⚡️ > we built claude code but as a game > your entire repo becomes an isometric city > files are buildings with the height determined by the number of files > choose your crew for a task aka your model > visualise agents constructing buildings (files) in realtime > open PRs are ships. navigate to a new island to visualise PRs and review the changes > built using the Claude sdk > software engineering is shifting towards managing multiple agents rather than reading file diffs. we don't want you to scroll reels while your agents do work. shoutout to team Devfolio as always for the best hackathons. big shoutout to the team Fahim Arjun R ♥️

Parth

15,574 次观看 • 6 天前

Introducing Kombai 2.0 - the first AI design engineer. We keep hearing that AGI is almost here. Still, we’re stuck with coding agents that don’t have taste and design tools that don’t understand our codebase. Both are artifacts of a world where design and engineering were two different jobs, with a handoff in between. That world is changing fast. Today, designers ship code, engineers want to escape handoffs, and everyone wants to build tasteful UX. Kombai is built for this new world. Design and engineering, finally on the same side.

Introducing Kombai 2.0 - the first AI design engineer. We keep hearing that AGI is almost here. Still, we’re stuck with coding agents that don’t have taste and design tools that don’t understand our codebase. Both are artifacts of a world where design and engineering were two different jobs, with a handoff in between. That world is changing fast. Today, designers ship code, engineers want to escape handoffs, and everyone wants to build tasteful UX. Kombai is built for this new world. Design and engineering, finally on the same side.

Dipanjan Dey

440,365 次观看 • 2 个月前

Today we’re launching the newest version of Paradigm When we started Paradigm, the goal was never to tack AI onto existing spreadsheets. It was to build a new type of interface that does the work for you. Now we’re pushing that vision much further. Workflows turn Paradigm into a system that runs research processes for you. Connect your CRM, existing spreadsheets, Slack, email, and internal data, and let Paradigm continuously run the research workflows your team already does. Same intuitive interface. But now a system of action. If you tried Paradigm before, try it again. Manual research is now a competitive liability.

Today we’re launching the newest version of Paradigm When we started Paradigm, the goal was never to tack AI onto existing spreadsheets. It was to build a new type of interface that does the work for you. Now we’re pushing that vision much further. Workflows turn Paradigm into a system that runs research processes for you. Connect your CRM, existing spreadsheets, Slack, email, and internal data, and let Paradigm continuously run the research workflows your team already does. Same intuitive interface. But now a system of action. If you tried Paradigm before, try it again. Manual research is now a competitive liability.

Anna Monaco

246,337 次观看 • 4 个月前

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

71,910 次观看 • 5 个月前

Temporal CEO Samar Birwadker says GitHub was designed for humans, but is now at the mercy of agents. "Agents are starting to get more and more long-lived, more asynchronous, and more mission-critical." "For example, if you pick coding agents alone, is something like GitHub was designed for humans collaborate and create [pull requests] right now." "Now a lot of code is being generated by these agents, and they're the ones creating these PRs essentially, and even code review process is being automated by other agents." "So now this entire system backend, which is being built for human consumption, is now at the mercy of these agents kind of using it for their own coordination and collaboration."

Temporal CEO Samar Birwadker says GitHub was designed for humans, but is now at the mercy of agents. "Agents are starting to get more and more long-lived, more asynchronous, and more mission-critical." "For example, if you pick coding agents alone, is something like GitHub was designed for humans collaborate and create [pull requests] right now." "Now a lot of code is being generated by these agents, and they're the ones creating these PRs essentially, and even code review process is being automated by other agents." "So now this entire system backend, which is being built for human consumption, is now at the mercy of these agents kind of using it for their own coordination and collaboration."

MTS

26,902 次观看 • 3 个月前

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!

Harjot Gill

4,775,791 次观看 • 3 个月前

Today starts Radical Speed Month at Automattic! Two-person teams, one month, building and shipping outside of our usual teams and approval processes. This is one of the most radical innovation initiatives I've ever been part of. I'm teaming up with Lucas Radke. We're building a tool to help creators find inspiration for their stories. We are working in public. Help us shape what we build!

Today starts Radical Speed Month at Automattic! Two-person teams, one month, building and shipping outside of our usual teams and approval processes. This is one of the most radical innovation initiatives I've ever been part of. I'm teaming up with Lucas Radke. We're building a tool to help creators find inspiration for their stories. We are working in public. Help us shape what we build!

Matthias Reinholz

13,014 次观看 • 3 个月前

I just closed a $70,000 deal with help from 10 Hermes agents Here is how it happened: A couple of months ago, one of my clients asked me to review their IT spending. The biggest surprise was Atlassian. They were using Jira, Confluence, Jira Service Management, and several paid plugins because the built in reporting and time tracking were not meeting their needs. With more than 300 users, they were spending around $140,000 every year. They had been paying that for six years. That is roughly $840,000. So I asked them: “If I build something that replaces most of these tools, improves the workflows your team struggles with, and cuts your bill in half, would you pay me $70,000 per year?” They said yes. So I put 10 Hermes agents to work For the next month, they worked alongside me for almost 8 hours a day. About half of the code was built using Fable 5 and the other half using Opus 4.8. I spent approximately $11,000 on tokens :P That sounds expensive until you compare it with a $70,000 yearly contract and a product I can now offer to other companies. One month later, the product was ready. The client loved it and gave me the green light to open it to the public and it's my code :) I called it Kapvel Kapvel includes: • Project management and Jira ticket imports • A full service desk with a customer portal • Built in time tracking and reporting • Documents with real time collaboration • Spreadsheets, presentations, and whiteboards • Electronic signatures and approvals • QA test case management • A dedicated UAT portal • GitHub, Bitbucket, and GitLab integrations • Pull request workflows inside the same platform • Custom themes and branded portals The part I am most excited about is what happens when someone submits a support ticket to me: My Hermes agents can immediately review the request, investigate the issue, and start working on a solution. Kapvel is basically: Jira + Confluence + DocuSign + Everhour + QA + UAT All inside one platform, with simpler pricing and fewer third party plugins. This is not a mockup The client is already using it Now I am preparing to open Kapvel to other teams Comment KAPVEL for early access.

I just closed a $70,000 deal with help from 10 Hermes agents Here is how it happened: A couple of months ago, one of my clients asked me to review their IT spending. The biggest surprise was Atlassian. They were using Jira, Confluence, Jira Service Management, and several paid plugins because the built in reporting and time tracking were not meeting their needs. With more than 300 users, they were spending around $140,000 every year. They had been paying that for six years. That is roughly $840,000. So I asked them: “If I build something that replaces most of these tools, improves the workflows your team struggles with, and cuts your bill in half, would you pay me $70,000 per year?” They said yes. So I put 10 Hermes agents to work For the next month, they worked alongside me for almost 8 hours a day. About half of the code was built using Fable 5 and the other half using Opus 4.8. I spent approximately $11,000 on tokens :P That sounds expensive until you compare it with a $70,000 yearly contract and a product I can now offer to other companies. One month later, the product was ready. The client loved it and gave me the green light to open it to the public and it's my code :) I called it Kapvel Kapvel includes: • Project management and Jira ticket imports • A full service desk with a customer portal • Built in time tracking and reporting • Documents with real time collaboration • Spreadsheets, presentations, and whiteboards • Electronic signatures and approvals • QA test case management • A dedicated UAT portal • GitHub, Bitbucket, and GitLab integrations • Pull request workflows inside the same platform • Custom themes and branded portals The part I am most excited about is what happens when someone submits a support ticket to me: My Hermes agents can immediately review the request, investigate the issue, and start working on a solution. Kapvel is basically: Jira + Confluence + DocuSign + Everhour + QA + UAT All inside one platform, with simpler pricing and fewer third party plugins. This is not a mockup The client is already using it Now I am preparing to open Kapvel to other teams Comment KAPVEL for early access.

Luke The Dev

23,021 次观看 • 18 天前

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

elvis

15,295 次观看 • 1 个月前

So excited to launch Autograph today. We raised $2.1M from elite operators, founders, and investors to build a platform that feels like God Mode for Operators. It's a single platform that integrates with existing systems — the alphabet soup of enterprise software, like your HRIS, ERP, FP&A, ATS, CRM, along with data warehouses and spreadsheets — to combine, clean, and make sense of your data. This data feeds a series of pre-built apps and agents that allow you to level up as an operator: run your complex, multi-functional workflows 10x better. We're solving the processes that takes forever and is really frustrating, but is essential to operating and scaling effectively: our first few apps are headcount planning, compensation reviews, and sales capacity. We're moving insanely fast. We're shipping a new app every couple of weeks. Soon, we'll have hiring pipelines, vendor analytics, resource allocation, unit economics, CX capacity, people analytics, and more. The best part? It's incredibly fast to set up thanks to our powerful agentic data engine, that processes any data source like magic. That means no long implementations, no multi-year contracts. We think it's the biggest leap forward for operators since the spreadsheet. Book an 20-minute onboarding to get started!

So excited to launch Autograph today. We raised $2.1M from elite operators, founders, and investors to build a platform that feels like God Mode for Operators. It's a single platform that integrates with existing systems — the alphabet soup of enterprise software, like your HRIS, ERP, FP&A, ATS, CRM, along with data warehouses and spreadsheets — to combine, clean, and make sense of your data. This data feeds a series of pre-built apps and agents that allow you to level up as an operator: run your complex, multi-functional workflows 10x better. We're solving the processes that takes forever and is really frustrating, but is essential to operating and scaling effectively: our first few apps are headcount planning, compensation reviews, and sales capacity. We're moving insanely fast. We're shipping a new app every couple of weeks. Soon, we'll have hiring pipelines, vendor analytics, resource allocation, unit economics, CX capacity, people analytics, and more. The best part? It's incredibly fast to set up thanks to our powerful agentic data engine, that processes any data source like magic. That means no long implementations, no multi-year contracts. We think it's the biggest leap forward for operators since the spreadsheet. Book an 20-minute onboarding to get started!

hari raghavan

83,565 次观看 • 9 个月前

Introducing Dune: a context-aware keypad for Mac that adapts to what you’re doing. Dune reads which app is in the foreground and automatically changes what its three keys do based on what you’re working on. One tap to join meetings without searching for links. Approve and merge PRs on GitHub. Approve or reject on Claude. Or trigger your own Agentic workflows. All from a single key press. Choose what Dune does from a set of pre-built workflow triggers or build your own. We are shipping a limited batch of Dune and would love to see what you build with it.

Introducing Dune: a context-aware keypad for Mac that adapts to what you’re doing. Dune reads which app is in the foreground and automatically changes what its three keys do based on what you’re working on. One tap to join meetings without searching for links. Approve and merge PRs on GitHub. Approve or reject on Claude. Or trigger your own Agentic workflows. All from a single key press. Choose what Dune does from a set of pre-built workflow triggers or build your own. We are shipping a limited batch of Dune and would love to see what you build with it.

Apoorv Shankar

304,897 次观看 • 4 个月前

The Marketing Engineer is the most important hire a marketing team can make in 2026. Not to run campaigns, but to build the agents that run them. Today we're introducing a new role to the marketing org: 𝗧𝗵𝗲 𝗠𝗮𝗿𝗸𝗲𝘁𝗶𝗻𝗴 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 We believe every business on the planet will eventually need one. Their job is to build the Agents, automations, and systems that create a new kind of marketing. Part-builder, part-strategist. They build Agents that monitor media coverage, flag sentiment shifts, and draft journalist outreach before your PR team even knows there's a story. They build Agents that track every competitor move, grade its severity, and rewrite your battle cards and talk tracks before your next sales call. They build Agents that turn every webinar into a brand-voice article, refreshed weekly and queued for your team to review before posting. Our first marketing hire Nick Lafferty has already become Profound's Founding Marketing Engineer, the first person to hold this title at a company fully behind it. Every marketing team on the planet will use AI to do their jobs better. But to build truly impactful systems, you need an owner and an orchestrator. That's the Marketing Engineer.

Dylan Babbs

324,105 次观看 • 4 个月前

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,475 次观看 • 4 个月前

Vikram-1 had to be big enough to carry the fuel to reach orbit, and smart enough to shed that weight along the way. Nearly as tall as a 7-storey building, getting something that size to orbit demands precision engineering at every stage of the climb, as much as it demands raw power. This episode is about how the team broke out of that loop and the systems that make it possible. #JourneyToOrbit #Vikram1

Vikram-1 had to be big enough to carry the fuel to reach orbit, and smart enough to shed that weight along the way. Nearly as tall as a 7-storey building, getting something that size to orbit demands precision engineering at every stage of the climb, as much as it demands raw power. This episode is about how the team broke out of that loop and the systems that make it possible. #JourneyToOrbit #Vikram1

Skyroot Aerospace

27,959 次观看 • 2 个月前

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents" "Close the loop, give the model a way to verify its own output" In a 20-minute session, an Anthropic Team member breaks down how to build agents that improve themselves The real setup is Claude running through loops, plan mode, and dynamic workflows Better than most $300 agent courses Bookmark and watch the talk Then read the article below

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents" "Close the loop, give the model a way to verify its own output" In a 20-minute session, an Anthropic Team member breaks down how to build agents that improve themselves The real setup is Claude running through loops, plan mode, and dynamic workflows Better than most $300 agent courses Bookmark and watch the talk Then read the article below

rari

381,585 次观看 • 1 个月前