正在加载视频...

视频加载失败

An engineer at Block (formerly Square) has an AI agent watching his screen all day. The engineer will discuss a feature with a colleague on Slack. A few hours later, the agent has already built the feature and opened a PR. This isn't some distant AI future. It's happening...

502,844 次观看 • 8 个月前 •via X (Twitter)

0 条评论

暂无评论

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

相关视频

My biggest takeaways from Dhanji Prasanna, CTO of Block: 1. Block’s internal AI agent "Goose" is saving employees on average 8 to 10 hours per week. The company built an open-source tool called Goose that handles tasks from organizing files to writing code. Across the entire company, they’re seeing roughly 20% to 25% of manual work hours saved, and that number keeps climbing. 2. Non-technical teams are getting the biggest productivity boost from AI, not engineers. People in legal, risk management, and operations are now building their own software tools that previously would have required months on an engineering team’s roadmap. What used to take weeks now takes hours, and employees do it themselves without waiting. 3. Changing organizational structure unlocked more productivity than any AI tool. To transform into a truly “technology driven” company, Block reorganized from separate business units (each with their own GM and engineering teams) to a single functional structure where all engineers report to one leader. This “boring” change enabled a unified technology strategy and drove more acceleration than any AI tool. 4. Code quality has almost nothing to do with product success. YouTube became one of Google’s most successful products despite storing videos as blobs in a MySQL database with a slow Python stack. Meanwhile, Google Video had superior technology with more formats and higher resolution but failed completely. The lesson: Focus on solving real problems for people, not on perfect code. 5. AI enables teams to explore multiple paths simultaneously instead of choosing one up front. Previously, limited resources meant teams had to pick their best guess for an experiment. Now AI can build multiple different approaches overnight, allowing teams to compare five or six options and throw away entire features if they don’t feel right—a practice that was unthinkable before. 6. Most successful products start as tiny experiments, not big initiatives. Cash App began as a hack-week idea. Goose started as one engineer’s side project. Block’s Bitcoin product came from a three-person hackathon team. In contrast, Google Wave had 70 to 80 engineers before having real users and failed. Small experiments that prove value beat large up-front investments. 7. Leaders must use AI tools daily to drive real organizational adoption. Block’s CEO Jack Dorsey, the CTO, and the entire executive team use Goose every single day. This hands-on experience teaches them how workflows actually change and drives authentic adoption throughout the organization far more than reading articles or attending conferences about AI. 8. AI excels at new projects but struggles with complex legacy systems. Teams building new applications or working on greenfield platforms see aggressive productivity gains. But in existing codebases with years of accumulated complexity, the gains aren’t there yet. Deploy AI where it works best rather than everywhere at once. 9. Giving away valuable technology for free can be a winning strategy. Block open-sourced Goose even though it could have been a standalone billion-dollar business. Even their competitors actively use it. The philosophy: build things that benefit everyone and outlast your own company. This commitment to open-source technology attracts talent and builds industry goodwill while advancing everyone’s capabilities. 10. Purpose should drive your technology choices, not the other way around. Rather than chasing every AI trend or trying to be at the forefront of every technology, identify what truly matters to your company and customers. Block stays focused on economic empowerment, which guides their technology decisions and keeps them from getting distracted by every new advancement. Listen now 👇 • YouTube: • Spotify: • Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 Sinch — Build messaging, email, and calling into your product: 🏆 Figma Make — A prompt-to-code tool for making ideas real: 🏆 — A global leader in digital identity verification: A

Lenny Rachitsky

812,117 次观看 • 8 个月前

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,343 次观看 • 1 年前

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

24,618 次观看 • 3 个月前

A founder turned down a $1M job offer from Meta to build a $5M ARR company with 9 people. His CAC is in cents. He has no sales team, no CS org, and no plans to build one (read on for the full playbook). Meet Ethan, the founder of Jobright, and if you are an early-stage lean AI company, this might be the most valuable thing you read this week. While every other AI startup was raising, hiring aggressively, and building org charts before they had customers, Ethan was talking to users (face-to-face). Their first million (revenue) was pure product-market fit mode. It came entirely from word of mouth, with users pulling in their friends because the product worked. The next four million came from clearly defining their ICP, tracking CAC, and obsessing over growth as a data-driven system. They built an experiment pipeline with a strict 7-day ship-or-kill rule. Channels that couldn't hit payback targets were automatically cut. And through all of it, the headcount barely moved. Because every time they spotted a repetitive workflow, their default instinct was to build an agent (when most founders hire). Their first internal AI agent took an enterprise manager from 5 accounts to 50, without any additional hires. Last month alone, they shipped 3 new internal agents: • An inbox agent that reads, classifies, and drafts responses • An ops agent that turns messy client requests into structured tasks • An outreach agent that finds relevant partners, writes personalized first messages, and runs follow-up sequences Each of those consumed hours of manual labor every week, but now they run on autopilot. That is what 9 people running like 50 looks like in practice. It is one of the best 0 to $5M stories I have come across in the lean AI space. So I spent hours going deep on every decision, system, and principle behind how they did this, and turned it into a super actionable playbook for founders who are pre-revenue or going from 0 to 1. Inside, you'll get: • The exact growth OS they used to go from $1M to $5M ARR • How they built internal agents that let 9 people do the work of 50 • The hiring filter that screens for true AI-native operators • The 2-question test every feature must pass before it gets built • How they structured growth after hitting PMF (the full funnel with owner metrics) • What building from $0 → $1M looks like vs. $1M → $5M • The data flywheel they've been compounding since day one that gets harder to replicate, and how to design yours from scratch Originally, I put this together as a resource for founders I work with directly. But the insights here are too actionable to keep internal, so I'm sharing them publicly. It's one of the most detailed operating blueprints I've put together for those aspiring to join the Lean AI Leaderboard. If you are one of them, grab this right away as it will save you months of expensive guesswork. Ethan, Eric, and team, welcome to the Lean AI Leaderboard!🚀 Link to the playbook:

Henry Shi

51,236 次观看 • 4 个月前

We use OpenClaws to do all of our work at Every 📧. We have 25 full-time employees, so we’re one of the few companies in the world that has seen how work changes when everyone has their own personal agent in the company Slack. I chatted with Every 📧 COO Brandon (Brandon Gell) and Every 📧 head of platform Willie (Willie) to share what we’ve learned. We get into: - Why agents become mirrors of their owners, and how that influences how other people on the team interact with them - How a parallel AI org chart forms on its own. People have stopped tagging me on Slack with questions about Proof, the document editor I vibe coded, because they knew my agent R2-C2 can step in - The etiquette for human-agent collaboration is being invented in real time. Brandon's rule is that if there's an established process or documented answer, always ask the agent, not their human - Why everyone is a manager now, and why even experienced managers carry limiting beliefs about what their agents can do - This is a must-watch for anyone trying to understand how AI workers change daily operations, not just in theory, but inside a company that’s half-agent Watch below! Timestamps Introduction: How Brandon built Zosia, an AI agent to run his household: Brandon’s “aha” moment: What happened when everyone on the team got their own agent: How agents take on their owners' personalities, and why that matters inside an org: Why it’s important for agents to work in public: What we’re still figuring out when it comes to agent behavior, including memory gaps, group chat etiquette, and the "ant death spiral" problem: How we built Plus One, our hosted OpenClaw product: The cultural shift required to make agents work at scale:

Dan Shipper 📧

67,958 次观看 • 3 个月前

Microsoft just banned its own engineers from using AI. The tool was literally costing MORE than the humans it was supposed to replace. They lied to you about AI adoption and now the whole narrative is blowing up: Microsoft gave thousands of engineers access to Claude Code six months ago and encouraged them to use it. Engineers loved it and adoption exploded. But then the invoices arrived. Token-based pricing means every query, every code review, every debugging session costs money. At scale across 100,000 engineers, the numbers became so large that Microsoft issued an internal order to cancel nearly all Claude Code licenses by end of June and force everyone onto their own cheaper tool instead. The company that invested $5 billion in Anthropic just told its own people to stop using Anthropic's product because it costs too much. Uber's story is even worse... Their CTO Praveen Neppalli Naga told The Information that the budget he planned for the full year was "blown away already" by April. Uber had rolled out Claude Code in December 2025. By March, 84% of their 5,000 engineers were using it with 70% of all committed code coming from AI systems. Heavy users were burning $500 to $2,000 per month each. Naga himself spent $1,200 in a single two-hour demo session. The company had even built internal leaderboards ranking engineers by how much AI they used. They literally gamified the spending and then ran out of money. Now look at what Nvidia's own VP of applied deep learning Bryan Catanzaro said to Axios last month. Direct quote: "For my team, the cost of compute is far beyond the costs of the employees." This is a VP at the company that SELLS the chips saying that using AI is more expensive than paying humans. Think about what this means for the entire AI narrative. Every CEO on every earnings call for the past two years has said the same thing: AI will make us more efficient, reduce headcount, and cut costs. The stock market rewarded every company that said it. Fired workers, stock goes up. Announced AI adoption, stock goes up. But the actual companies deploying AI at scale are discovering the math doesn't work. The MORE employees use AI, the HIGHER the bill. Goldman Sachs forecasts a 24x increase in token consumption by 2030 as companies adopt AI agents. Gartner just published a report showing that even though individual token prices will drop 90% by 2030, total enterprise AI costs will go UP because agents consume exponentially more tokens per task than basic tools. Meta built an internal dashboard called "Claudeonomics" to track which employees use the most AI. Amazon started pushing engineers to "tokenmaxx," their internal term for consuming as many AI tokens as possible. Both companies are spending hundreds of billions on AI infrastructure this year alone. And Microsoft, the company that bet its entire future on AI, just told 100,000 engineers to stop using the tool they liked best because the per-token bills got out of control. The companies building AI are telling investors it saves money. The companies using AI are finding out it costs more than the humans it was supposed to replace. And even the company that makes the chips just admitted it through its own VP. This is the gap nobody on Wall Street is pricing in. $725 billion in AI infrastructure spending this year across Big Tech. And the first companies to actually deploy these tools at scale are already pulling back because the economics don't work. What do you think?

Ricardo

2,962,125 次观看 • 2 个月前

🚨 Claude Code costs $200/month. GitHub Copilot costs $19/month. Jack Dorsey's company built a free alternative. 35,000 GitHub stars. It's called Goose. An open source AI agent built by Block that goes beyond code suggestions. It installs, executes, edits, and tests. With any LLM you choose. Not autocomplete. Not suggestions. A full autonomous agent that takes actions on your computer. No vendor lock-in. No monthly subscription. Bring your own model. Here's what Goose does: → Works with ANY LLM. Claude, GPT, Gemini, Llama, DeepSeek, Ollama. Your choice. → Reads and understands your entire codebase → Writes, edits, and refactors code across multiple files → Runs shell commands and installs dependencies → Executes and debugs your code automatically → Extensible through MCP. Connect it to any external tool. → Desktop app, CLI, and web interface. Pick your workflow. → Written in Rust. Fast. Lightweight. No bloat. Here's the wildest part: Block is a $40 billion company. They built Cash App, Square, and TIDAL. They use Goose internally. Then they open sourced the entire thing. This isn't a side project from a random developer. This is production-grade tooling from a company that processes billions in payments. Built for their own engineers. Given to everyone. Claude Code: $200/month. Locked to Claude. GitHub Copilot: $19/month. Locked to GitHub. Cursor: $20/month. Locked to their editor. Goose: Free. Any LLM. Any editor. Any workflow. Forever. 35.3K GitHub stars. 3.3K forks. 4,078 commits. Built by Block. 100% Open Source. Apache 2.0 License.

Nav Toor

392,798 次观看 • 3 个月前

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

MIKE

38,108 次观看 • 22 天前