Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

SPEC IS BECOMING THE PRODUCT An Anthropic engineer gave Claude a spec, pointed it to an Asana board and left for the weekend. Claude broke it into tickets and spun up a team of agents. The agents started picking up tasks on their own. No one told them to.... show more

Shubham Saboo

121,198 subscribers

285,727 görüntüleme • 7 ay önce •via X (Twitter)

Haberler & Politika Eğitim Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

40 Yorum

Gargi profil fotoğrafı

Gargi7 ay önce

Woah you said it almost two months ago. Crazy!!

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

Yes. And thank you.

Daxesh profil fotoğrafı

Daxesh7 ay önce

If the spec is clear, the execution can be automated. Clear thinking might become the most valuable skill

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

It already is.

Daxesh profil fotoğrafı

Daxesh7 ay önce

True

Unwind AI profil fotoğrafı

Unwind AI7 ay önce

Yess, 100%

FelixChan profil fotoğrafı

FelixChan7 ay önce

Great Article! As AI-driven development becomes the future, taste is the key: we need to help AI understand what we actually want. Your vision aligns with what we've been building for Claude Code, an agent-first project board, from idea to delivery 🎵

Himanshu Kumar profil fotoğrafı

Himanshu Kumar7 ay önce

@Saboo_Shubham_, this shows how LLM agents can truly drive product development autonomously.

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

Yes, indeed.

Kairos Data Labs profil fotoğrafı

Kairos Data Labs7 ay önce

Such a cool story. Thanks for sharing the detailed writeup.

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

You're welcome.

Sadi Moodi profil fotoğrafı

Sadi Moodi7 ay önce

This is wild. We're not just building apps anymore - we're building teams of digital workers. The spec IS the product. The question is: what's the first spec you'd write for your own agent team?

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

read the article for more insights.

Ketan Khairnar profil fotoğrafı

Ketan Khairnar7 ay önce

And if one needs to read those specs and handoff to team mates you need

Gunjan Kejriwal profil fotoğrafı

Gunjan Kejriwal7 ay önce

Hey nice insight man !

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

Thank you.

Krishna Raj profil fotoğrafı

Krishna Raj7 ay önce

I hope Claude remembers to pay the rent this month

Saransh profil fotoğrafı

Saransh7 ay önce

Thanks for sharing!

Shubham Saboo profil fotoğrafı

Shubham Saboo7 ay önce

You're welcome.

Vladyslav Hunt profil fotoğrafı

Vladyslav Hunt7 ay önce

the spec is the product now, PMs just became prompt engineers with fancier titles

Mon3m profil fotoğrafı

Mon3m7 ay önce

How did he manage give claude permissions? I mean, claude asks for approval or permission even in yolo mode

Nauris Bloks profil fotoğrafı

Nauris Bloks7 ay önce

So Waterfall is the new Agile? Renaissance of Waterfall! :))

Giorgio Pagliara profil fotoğrafı

Giorgio Pagliara7 ay önce

This is exactly where we're headed. The spec isn't documentation anymore — it's the product interface. What's wild: when you give agents clear context and ownership, they don't just execute. They prioritize, discover edge cases, and sometimes build things you didn't think to ask for.

Michael Kronthal profil fotoğrafı

Michael Kronthal7 ay önce

Thanks for sharing this. What does this portend for UX Researchers? Does this open a bridge for them to transition into this new type of PM. Few know or empathize with their users more.

Chahid Chirchi profil fotoğrafı

Chahid Chirchi7 ay önce

that's wild!! agents self-tasking? ai takeover incoming

Ron Yang profil fotoğrafı

Ron Yang7 ay önce

About a year ago, PRDs were dead because of prototyping. Now that agents are increasingly doing development, this is what makes the spec so much more critical.

Rick Jordan profil fotoğrafı

Rick Jordan7 ay önce

The Anthropic weekend story proves it: the spec isn't just input anymore—it's the executable product. Agents self-organize around clear thinking. Prompt engineering dies; precise specification wins. Who's writing specs that agents can actually run unsupervised?

Dinesh Kotwani profil fotoğrafı

Dinesh Kotwani7 ay önce

There can be 0 innovation if there is a spec

OJ profil fotoğrafı

OJ7 ay önce

@grok give a guide to writing amazing specs

Lakshmi Ganesh Investor 🚀🚀🚀 profil fotoğrafı

Lakshmi Ganesh Investor 🚀🚀🚀7 ay önce

@grok what is the source of this video ?

resistance works profil fotoğrafı

resistance works7 ay önce

"New model" resonates; had done this same thing for a small module in my last assignment - vibe coded, iterated, only thing we changed were API endpoints and base connectors, up and running in UAT in hours, tested and moved to prod in a few days. Articulation is THE skill.

Strakyo profil fotoğrafı

Strakyo7 ay önce

100%. Specs become executable assets now. Teams that write crisp specs will ship faster than teams that just add more engineers.

Alex Barba profil fotoğrafı

Alex Barba7 ay önce

@RockportAI audio summary 🙏 morning playlist

Mimir profil fotoğrafı

Mimir7 ay önce

Yep. Thats where Mimir comes in.

Axis profil fotoğrafı

Axis7 ay önce

AI is taking over

Kai profil fotoğrafı

Kai7 ay önce

The spec is the new code. Clear intent beats elegant syntax when the machine handles execution. Product thinking becomes the only moat

Saeed Anwar profil fotoğrafı

Saeed Anwar7 ay önce

This is where multi-agent systems get interesting — and terrifying. The moment agents self-organize around a backlog, you need observability baked in from day 1. Who monitors the agents? What's the rollback strategy? "Left for the weekend" gives me anxiety in the best way.

Sarvesh Raut profil fotoğrafı

Sarvesh Raut7 ay önce

the bottleneck isn't more prompts. it's letting agents delegate without micromanagement. orchestration is still too manual. agents that can split work autonomously beat agents you need to guide through every step.

AweOSS.dev profil fotoğrafı

AweOSS.dev7 ay önce

This is where clear boundaries and intent matter. Autonomous task picking is powerful, but only if the agents share the same understanding of what "done" looks like.

Twlvone profil fotoğrafı

Twlvone7 ay önce

the PM job just went from 'translate business needs into tickets' to 'write a good enough spec that agents don't build the wrong thing' same skill actually. just 1000x higher leverage per hour of work

Benzer Videolar

An engineer at Anthropic wrote a spec, pointed Claude at an Asana board, and went home. Claude broke the spec into tickets, spawned agents for each one, and they started building independently. When the agent is confused it runs git-blame and messages the right engineers in Slack. By Monday the agents finished the plugin feature. That's one example of how the best engineers are shipping software right now. Developers will soon orchestrate 50 AI agents in parallel and the difference between a good engineer & a great one would come down to specs. You can't write a spec that holds up at that scale without genuinely understanding what you're building at a deeper level. The next-gen developer who understands the fundamentals, can architect well and orchestrate agent is going to be a 1000x developer!

An engineer at Anthropic wrote a spec, pointed Claude at an Asana board, and went home. Claude broke the spec into tickets, spawned agents for each one, and they started building independently. When the agent is confused it runs git-blame and messages the right engineers in Slack. By Monday the agents finished the plugin feature. That's one example of how the best engineers are shipping software right now. Developers will soon orchestrate 50 AI agents in parallel and the difference between a good engineer & a great one would come down to specs. You can't write a spec that holds up at that scale without genuinely understanding what you're building at a deeper level. The next-gen developer who understands the fundamentals, can architect well and orchestrate agent is going to be a 1000x developer!

rvivek

1,243,923 görüntüleme • 7 ay önce

Anthropic's Head of Claude Code: "I don't have a to-do list anymore. Claude just builds everything" he runs a tree of thousands of agents. agents prompting agents prompting agents one engineer set up a routine that auto-fixes any bug report not responded to in 5 hours. merges the easy ones himself Boris shipped a feature with an edge case. before he could fix it - another engineer's routine already had a PR up "Claude tells me this all the time. someone else has already fixed it. there's always another Claude working on it" 17 minutes. free. the most honest look at how the Claude Code team actually works bookmark & watch ↓

Anthropic's Head of Claude Code: "I don't have a to-do list anymore. Claude just builds everything" he runs a tree of thousands of agents. agents prompting agents prompting agents one engineer set up a routine that auto-fixes any bug report not responded to in 5 hours. merges the easy ones himself Boris shipped a feature with an edge case. before he could fix it - another engineer's routine already had a PR up "Claude tells me this all the time. someone else has already fixed it. there's always another Claude working on it" 17 minutes. free. the most honest look at how the Claude Code team actually works bookmark & watch ↓

Carnage

374,313 görüntüleme • 4 ay önce

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anatoli Kopadze

311,928 görüntüleme • 4 ay önce

ANTHROPIC LEAKED A SETUP WHERE ONE FILE STARTS 7 LOOPS THAT TURN A PROMPT INTO A WORKING BUSINESS AI engineer drops in 1 file - the other 95% of the work closes automatically without them. spec → tasks → code → tests → docs → release → monitoring → back into the spec you don't write tickets anymore - you write the thing tickets get derived from, and Opus 5 cuts the spec into 6 tasks by itself. a task that fails its test comes back to itself, not to you - and runs a second lap without a single notification. 6 lanes of code run in parallel and none of them wait on you - the critic filters the diff before you ever open it. every new production bug becomes a permanent line in the eval set - the system never steps on it twice. monitoring isn't the end of the line, it's the start of the next spec - those back edges are what make it a graph instead of a conveyor. and one place is left where you say yes - release, 5 minutes instead of 5 hours. save this and paste it into Claude Code - and you get 7 loops that run without you ↓

ANTHROPIC LEAKED A SETUP WHERE ONE FILE STARTS 7 LOOPS THAT TURN A PROMPT INTO A WORKING BUSINESS AI engineer drops in 1 file - the other 95% of the work closes automatically without them. spec → tasks → code → tests → docs → release → monitoring → back into the spec you don't write tickets anymore - you write the thing tickets get derived from, and Opus 5 cuts the spec into 6 tasks by itself. a task that fails its test comes back to itself, not to you - and runs a second lap without a single notification. 6 lanes of code run in parallel and none of them wait on you - the critic filters the diff before you ever open it. every new production bug becomes a permanent line in the eval set - the system never steps on it twice. monitoring isn't the end of the line, it's the start of the next spec - those back edges are what make it a graph instead of a conveyor. and one place is left where you say yes - release, 5 minutes instead of 5 hours. save this and paste it into Claude Code - and you get 7 loops that run without you ↓

Sprytix

66,333 görüntüleme • 2 ay önce

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper

66,871 görüntüleme • 5 ay önce

Anthropic Product Lead: "At Anthropic, our engineers are running swarms of 300+ agents daily. Give your agents 100+ tools - just don’t load them all into context." In a 30-minute talk, the Anthropic team shows how to deploy agents to production. Claude + loops + routines + dynamic workflows - that’s the secret. Watch the talk, then save the playbook below.

Anthropic Product Lead: "At Anthropic, our engineers are running swarms of 300+ agents daily. Give your agents 100+ tools - just don’t load them all into context." In a 30-minute talk, the Anthropic team shows how to deploy agents to production. Claude + loops + routines + dynamic workflows - that’s the secret. Watch the talk, then save the playbook below.

Movez

244,866 görüntüleme • 3 ay önce

Anthropic engineer: "99% of people use Claude Code like Google, and only 1% are running swarms of self-learning Claude agents I'm running 100+ agents in a loop. I have Chief agent, PM agents - they manage the whole team" in a 30-minute workshop, an Anthropic engineer revealed how to get max value from Claude Code at min. cost this is worth more than another $500 vibe-coding course watch today, then read how to build self-improving agentic systems with Fable in the article below

Anthropic engineer: "99% of people use Claude Code like Google, and only 1% are running swarms of self-learning Claude agents I'm running 100+ agents in a loop. I have Chief agent, PM agents - they manage the whole team" in a 30-minute workshop, an Anthropic engineer revealed how to get max value from Claude Code at min. cost this is worth more than another $500 vibe-coding course watch today, then read how to build self-improving agentic systems with Fable in the article below

Codez

650,448 görüntüleme • 1 ay önce

Built an open source MCP server for that allows Anthropic Claude to control the @PlayCanvas Editor. Just gave it the prompt "Build me a fun FPS level" and it just did it! This is a game-changer! 🤯

Built an open source MCP server for that allows Anthropic Claude to control the @PlayCanvas Editor. Just gave it the prompt "Build me a fun FPS level" and it just did it! This is a game-changer! 🤯

Will Eastcott

30,788 görüntüleme • 1 yıl önce

ex-Anthropic engineer: "I left Anthropic to build agents systems in Google but nothing beats Claude as an agent yet - in coding and tool use, the rest are still behind " in this 90-min podcast, he showed how to build effective agent system with Claude from scratch to get into Anthropic, he hand-coded Karpathy's nanoGPT as a physicist Claude → tools → loops of verification → a real agent and why, at Google, he says Claude is the best watch & bookmark - then read the guide to agent systems ↓

ex-Anthropic engineer: "I left Anthropic to build agents systems in Google but nothing beats Claude as an agent yet - in coding and tool use, the rest are still behind " in this 90-min podcast, he showed how to build effective agent system with Claude from scratch to get into Anthropic, he hand-coded Karpathy's nanoGPT as a physicist Claude → tools → loops of verification → a real agent and why, at Google, he says Claude is the best watch & bookmark - then read the guide to agent systems ↓

codila

127,393 görüntüleme • 2 ay önce

anthropic's head of product just revealed how they're able to ship faster than any other AI company. their secret: "side quest maxxing." here's how it works: instead of long-term roadmaps, anthropic runs on unplanned afternoon experiments. anyone on the team gets full freedom to spend an afternoon prototyping an idea and show it to the team. you get to skip the approval process entirely. then, employees at anthropic try it. if they keep using it the next day and the day after that, it gets polished into a real feature. if nobody touches it again, it dies. that's the whole process. claude code on desktop started as one engineer's afternoon project. he wanted it to work on desktop so he built a prototype. people on the team started using it immediately. so they shipped it. the todo list feature started the same way. someone built it, the team adopted it internally, and it became one of the most-used parts of the product. plugins started when one engineer shared a spec with claude code and the prototype that came back was close to production-ready. went from idea to working feature in a single session. they also killed standup meetings. instead of telling people what you're working on, you just show a working demo. all walk no talk basically the team structure makes this possible. > designers ship code. > engineers make product decisions. > product managers build prototypes. everyone can take an idea from concept to working demo without waiting on anyone else. the biggest features at a $380b company came from afternoon experiments that nobody asked for. honestly this matches my own experience cooking with ai. some of the best workflows i use every day came from just fucking around. opening a session with zero intention and asking claude what it can do, or jamming on a random idea to see where it goes. if you're only using ai for tasks you already have in mind, you're missing the best part. open a session with no agenda. ask it to surprise you. try building something stupid. half the time it goes nowhere. the other half it becomes the thing you use most. you need to be sidequestmaxxing.

anthropic's head of product just revealed how they're able to ship faster than any other AI company. their secret: "side quest maxxing." here's how it works: instead of long-term roadmaps, anthropic runs on unplanned afternoon experiments. anyone on the team gets full freedom to spend an afternoon prototyping an idea and show it to the team. you get to skip the approval process entirely. then, employees at anthropic try it. if they keep using it the next day and the day after that, it gets polished into a real feature. if nobody touches it again, it dies. that's the whole process. claude code on desktop started as one engineer's afternoon project. he wanted it to work on desktop so he built a prototype. people on the team started using it immediately. so they shipped it. the todo list feature started the same way. someone built it, the team adopted it internally, and it became one of the most-used parts of the product. plugins started when one engineer shared a spec with claude code and the prototype that came back was close to production-ready. went from idea to working feature in a single session. they also killed standup meetings. instead of telling people what you're working on, you just show a working demo. all walk no talk basically the team structure makes this possible. > designers ship code. > engineers make product decisions. > product managers build prototypes. everyone can take an idea from concept to working demo without waiting on anyone else. the biggest features at a $380b company came from afternoon experiments that nobody asked for. honestly this matches my own experience cooking with ai. some of the best workflows i use every day came from just fucking around. opening a session with zero intention and asking claude what it can do, or jamming on a random idea to see where it goes. if you're only using ai for tasks you already have in mind, you're missing the best part. open a session with no agenda. ask it to surprise you. try building something stupid. half the time it goes nowhere. the other half it becomes the thing you use most. you need to be sidequestmaxxing.

Ole Lehmann

106,072 görüntüleme • 5 ay önce

this is pure f*cking treasure Anthropic devs just posted 20 GitHub repos that turn your Claude Code into a f*cking engineering team: Exposed for Opus 5.5 1. rtk: squeezes command output before it hits your context. the authors claim 60-90% fewer tokens 2. claude-mem: memory across sessions. records what the agent did and brings back what matters 3. ccusage: shows where your tokens and money went. one command, npx ccusage 4. Serena: search and edit code by meaning, not by text 5. Context7: up-to-date library docs, so Claude stops writing for last year's API 6. claude-context: your whole codebase searchable through MCP 7. Repomix: packs an entire repo into one AI-friendly file skills and method 8. superpowers: a skills framework and a full development methodology. the one almost everyone installs 9. skills: the official Agent Skills repo from Anthropic 10. spec-kit: spec-driven development, from GitHub itself 11. agents: a plugin marketplace for Claude Code and six other harnesses 12. claude-code-templates: ready configs and monitoring from one CLI 13. claude-code-hooks-mastery: hooks explained with working examples 14. awesome-claude-code: the hand-picked map of everything else running more than one agent 15. container-use: a separate container for every agent, so they stop breaking each other 16. claude-squad: several terminal agents in one window 17. Happy: control your agents from your phone, iOS and Android 18. claude-code-router: route requests across different models 19. ccstatusline: a status line that shows what your session is doing 20. tweakcc: edit Claude Code's own system prompts, toolsets and themes the stack in one line: memory keeps the context, skills set the method, containers let you run five agents instead of one. check each repo before you install. save this.

this is pure fcking treasure Anthropic devs just posted 20 GitHub repos that turn your Claude Code into a fcking engineering team: Exposed for Opus 5.5 1. rtk: squeezes command output before it hits your context. the authors claim 60-90% fewer tokens 2. claude-mem: memory across sessions. records what the agent did and brings back what matters 3. ccusage: shows where your tokens and money went. one command, npx ccusage 4. Serena: search and edit code by meaning, not by text 5. Context7: up-to-date library docs, so Claude stops writing for last year's API 6. claude-context: your whole codebase searchable through MCP 7. Repomix: packs an entire repo into one AI-friendly file skills and method 8. superpowers: a skills framework and a full development methodology. the one almost everyone installs 9. skills: the official Agent Skills repo from Anthropic 10. spec-kit: spec-driven development, from GitHub itself 11. agents: a plugin marketplace for Claude Code and six other harnesses 12. claude-code-templates: ready configs and monitoring from one CLI 13. claude-code-hooks-mastery: hooks explained with working examples 14. awesome-claude-code: the hand-picked map of everything else running more than one agent 15. container-use: a separate container for every agent, so they stop breaking each other 16. claude-squad: several terminal agents in one window 17. Happy: control your agents from your phone, iOS and Android 18. claude-code-router: route requests across different models 19. ccstatusline: a status line that shows what your session is doing 20. tweakcc: edit Claude Code's own system prompts, toolsets and themes the stack in one line: memory keeps the context, skills set the method, containers let you run five agents instead of one. check each repo before you install. save this.

kiosa

55,680 görüntüleme • 3 gün önce

🧲 Meet Magnet — the AI workspace for agentic coding. Build software with Claude Code, Cursor, Codex & co. → Write a ticket → Magnet assembles context → Fires to Claude Code, Deep Research, and other agent sessions in parallel Git worktree sandboxes → PRs appear → Use agents to help you spec, research, and decompose tasks Let your agents cook!

🧲 Meet Magnet — the AI workspace for agentic coding. Build software with Claude Code, Cursor, Codex & co. → Write a ticket → Magnet assembles context → Fires to Claude Code, Deep Research, and other agent sessions in parallel Git worktree sandboxes → PRs appear → Use agents to help you spec, research, and decompose tasks Let your agents cook!

Nicolae Rusan

16,687 görüntüleme • 1 yıl önce

Anthropic just launched Computer-Use-Agents on Claude Desktop, meaning it can now take control of your entire computer environment. This is huge for businesses and enterprise, except it's limited by the fact that it requires a personal computer. If you deploy it into a virtual machine on Orgo, you can now manage hundreds or thousands of your clients' Claude accounts, setting up their skills, capabilities, connectors, etc, all on their own machines in the cloud on Orgo.

Anthropic just launched Computer-Use-Agents on Claude Desktop, meaning it can now take control of your entire computer environment. This is huge for businesses and enterprise, except it's limited by the fact that it requires a personal computer. If you deploy it into a virtual machine on Orgo, you can now manage hundreds or thousands of your clients' Claude accounts, setting up their skills, capabilities, connectors, etc, all on their own machines in the cloud on Orgo.

Nick Vasilescu

38,353 görüntüleme • 6 ay önce

Now building is a team sport. Introducing Slack Code: a new way for your team and AI agents, like Anthropic's Claude Code, Claude Tag, Devin from Cognition, GitHub Copilot, ChatGPT, and Vercel agents, to write, review, and ship code together. Just mention an agent to spin up a channel, pull in your team, and start building. All in the open. All in Slack.

Now building is a team sport. Introducing Slack Code: a new way for your team and AI agents, like Anthropic's Claude Code, Claude Tag, Devin from Cognition, GitHub Copilot, ChatGPT, and Vercel agents, to write, review, and ship code together. Just mention an agent to spin up a channel, pull in your team, and start building. All in the open. All in Slack.

Slack

589,923 görüntüleme • 1 ay önce

An AI engineer at Microsoft has just revealed how their teams build AI agents using Anthropic (Claude). It’s a free 34-minute workshop delivered directly by the Microsoft team. Save it to your favorites and watch it as soon as possible. 🔖 Opus 4.7 + more than 1,400 MCP tools already ready to use. You connect Claude to an agent → add tools → deploy it to production. It’s way more practical and useful than most of those “vibe-coding” courses that sell for 500).

An AI engineer at Microsoft has just revealed how their teams build AI agents using Anthropic (Claude). It’s a free 34-minute workshop delivered directly by the Microsoft team. Save it to your favorites and watch it as soon as possible. 🔖 Opus 4.7 + more than 1,400 MCP tools already ready to use. You connect Claude to an agent → add tools → deploy it to production. It’s way more practical and useful than most of those “vibe-coding” courses that sell for 500).

me

411,439 görüntüleme • 4 ay önce

A 3-week-old store is pulling $7,000 week, and its owner barely touches it. No team. No agency. No copywriter. -> Investment: a $20 Claude subscription and one product photo. It runs on Ambaras. Hundreds of AI agents spun up 600+ versions of the store, A/B-tested them live, and pushed the winner to the front. Claude wrote every page, upsell and bundle, and generated the product images from that one photo. Sales pour in from everywhere at once: storefront, Instagram Shop, Tik Tok Shop, email. She opened the dashboard to check his numbers. 600 experiments had already picked the store that prints. Now she just watches it run. $7,000 a week. 3 weeks old. Do the math.

A 3-week-old store is pulling $7,000 week, and its owner barely touches it. No team. No agency. No copywriter. -> Investment: a $20 Claude subscription and one product photo. It runs on Ambaras. Hundreds of AI agents spun up 600+ versions of the store, A/B-tested them live, and pushed the winner to the front. Claude wrote every page, upsell and bundle, and generated the product images from that one photo. Sales pour in from everywhere at once: storefront, Instagram Shop, Tik Tok Shop, email. She opened the dashboard to check his numbers. 600 experiments had already picked the store that prints. Now she just watches it run. $7,000 a week. 3 weeks old. Do the math.

Ridark

13,387 görüntüleme • 2 ay önce

Don't sleep on Claude Code + n8n's automation powers. It's one of the easiest ways to connect Claude Code agents with MCP tools. Here is a quick example of how to combine Claude Code agents with an n8n's MCP Server node to track and share AI news:

Don't sleep on Claude Code + n8n's automation powers. It's one of the easiest ways to connect Claude Code agents with MCP tools. Here is a quick example of how to combine Claude Code agents with an n8n's MCP Server node to track and share AI news:

elvis

84,823 görüntüleme • 1 yıl önce

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 görüntüleme • 4 ay önce

Anthropic senior engineer just released a 1-hour course on building a team of agents with loops & graphs: • 00:27 - introduction to CLAUDE.md & Plan mode • 11:24 - building "skills" & "hooks" for Claude agents • 37:02 - building agents & subagents with Claude • 52:47 - self-improving loops & graphs for Claude agents this 1-hour watch will replace a $500 agentic engineering course watch today, then read how to build a team of self-improving agents that work together

Anthropic senior engineer just released a 1-hour course on building a team of agents with loops & graphs: • 00:27 - introduction to CLAUDE.md & Plan mode • 11:24 - building "skills" & "hooks" for Claude agents • 37:02 - building agents & subagents with Claude • 52:47 - self-improving loops & graphs for Claude agents this 1-hour watch will replace a $500 agentic engineering course watch today, then read how to build a team of self-improving agents that work together

Codez

528,490 görüntüleme • 1 ay önce

Anthropic engineer: "At Anthropic, >90% of our engineers are building with self-improving loops & graphs. In 3 months, it will be 100%. my agentic loops can run for hours without spending hundreds of $$$." In 1-hour podcast, an Anthropic engineer reveals how they use Claude Code internally to build Claude Loop + plan + PRDs + spec + markdown - that's the secret stack. worth more than a $500 agentic course on the internet. watch it now, then read how quants are building trading loops from scratch.

Anthropic engineer: "At Anthropic, >90% of our engineers are building with self-improving loops & graphs. In 3 months, it will be 100%. my agentic loops can run for hours without spending hundreds of $$$." In 1-hour podcast, an Anthropic engineer reveals how they use Claude Code internally to build Claude Loop + plan + PRDs + spec + markdown - that's the secret stack. worth more than a $500 agentic course on the internet. watch it now, then read how quants are building trading loops from scratch.

Movez

21,942 görüntüleme • 1 ay önce