正在加载视频...

视频加载失败

返回首页

The internet is getting agentified Winners make agents deployable. Routable. Trusted. New distribution is agent-first Your audience isn’t developers It’s their agents Dedalus Labs = Vercel for AI Agents What it does (so you ship): • Hosts your MCP servers on their cloud • Autoscaling + load balancing handled...

davj's profile picture

David J Phillips

20,308 subscribers

27,396 次观看 • 6 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

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

相关视频

If your MCP server has dozens of tools, it’s probably built wrong. You need tools that are specific and clear for each use case—but you also can’t have too many. This creates an almost impossible tradeoff that most companies don’t know how to solve. That’s why I interviewed my friend Alex Rattray (Alex Rattray), the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. I had him on Every 📧’s AI & I to talk about MCP and the future of the AI-native internet. We get into: • Design MCP servers to be lean and precise. Alex’s best practices for building reliable MCP servers start with keeping the toolset small, giving each tool a precise name and description, and minimizing the inputs and outputs the model has to handle. At Stainless, they also often add a JSON filter on top to strip out unnecessary data. • Make complex APIs manageable with dynamic mode. To solve the problem of how an AI figures out which tool to use in larger APIs, Stainless switches to “dynamic mode,” where the model gets only three tools: List the endpoints, pick one and learn about it, and then execute it. • MCP servers as business copilots. At Stainless, Alex uses MCP servers to connect tools like Notion and HubSpot, so he can ask questions like, “Which customers signed up last week?” The system queries multiple databases and returns a summary that would’ve otherwise taken multiple logins and searches. • Create a “brain” for your company with Claude Code. Alex built a shared company brain at Stainless by keeping Claude Code running on his system and asking it to save useful inputs—like customer feedback and SQL queries—into GitHub. Over time, this creates a curated archive his team can query easily. • The future of MCP is code execution. Instead of giving models hundreds of tools, Alex believes the most powerful setup will be a simple code execution tool and a doc search tool. The AI writes code against an API’s SDK, runs it on a server, and checks the docs when it gets stuck. This is a must-watch for anyone who wants to understand MCP—and learn how to use them as a competitive edge. Watch below! Timestamps: Introduction: 00:01:14 Why Alex likes running barefoot: 00:02:54 APIs and MCP, the connectors of the new internet: 00:05:09 Why MCP servers are hard to get right: 00:10:53 Design principles for reliable MCP servers: 00:20:07 Scaling MCP servers for large APIs: 00:23:50 Using MCP for business ops at Stainless: 00:25:14 Building a company brain with Claude Code: 00:28:12 Where MCP goes from here: 00:33:59 Alex’s take on the security model for MCP: 00:41:10
51:39

If your MCP server has dozens of tools, it’s probably built wrong. You need tools that are specific and clear for each use case—but you also can’t have too many. This creates an almost impossible tradeoff that most companies don’t know how to solve. That’s why I interviewed my friend Alex Rattray (Alex Rattray), the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. I had him on Every 📧’s AI & I to talk about MCP and the future of the AI-native internet. We get into: • Design MCP servers to be lean and precise. Alex’s best practices for building reliable MCP servers start with keeping the toolset small, giving each tool a precise name and description, and minimizing the inputs and outputs the model has to handle. At Stainless, they also often add a JSON filter on top to strip out unnecessary data. • Make complex APIs manageable with dynamic mode. To solve the problem of how an AI figures out which tool to use in larger APIs, Stainless switches to “dynamic mode,” where the model gets only three tools: List the endpoints, pick one and learn about it, and then execute it. • MCP servers as business copilots. At Stainless, Alex uses MCP servers to connect tools like Notion and HubSpot, so he can ask questions like, “Which customers signed up last week?” The system queries multiple databases and returns a summary that would’ve otherwise taken multiple logins and searches. • Create a “brain” for your company with Claude Code. Alex built a shared company brain at Stainless by keeping Claude Code running on his system and asking it to save useful inputs—like customer feedback and SQL queries—into GitHub. Over time, this creates a curated archive his team can query easily. • The future of MCP is code execution. Instead of giving models hundreds of tools, Alex believes the most powerful setup will be a simple code execution tool and a doc search tool. The AI writes code against an API’s SDK, runs it on a server, and checks the docs when it gets stuck. This is a must-watch for anyone who wants to understand MCP—and learn how to use them as a competitive edge. Watch below! Timestamps: Introduction: 00:01:14 Why Alex likes running barefoot: 00:02:54 APIs and MCP, the connectors of the new internet: 00:05:09 Why MCP servers are hard to get right: 00:10:53 Design principles for reliable MCP servers: 00:20:07 Scaling MCP servers for large APIs: 00:23:50 Using MCP for business ops at Stainless: 00:25:14 Building a company brain with Claude Code: 00:28:12 Where MCP goes from here: 00:33:59 Alex’s take on the security model for MCP: 00:41:10

Dan Shipper 📧

15,645 次观看 • 9 个月前

We just raised an $11M seed to help developers build complex agents across any model and any tool in 5 lines of code. Our round was led by Kindred Ventures (steve jang) and Saga (Max Altman, Ben Braverman, Thomson Nguyen). At Dedalus Labs, we believe the future of AI agents isn’t linear or deterministic. Agents should know when to stop, when to branch, when to reattempt a task, and when to pause and ask for context. As a developer, we make your job simple: define the prompt, select the right tools and guardrails, and let your agent run. We were tired of writing hundreds of lines of code and battling Dockerfiles and infra—all for a spaghetti agent that breaks under stress. With Dedalus, you don’t have to do things the hard way. Our open-source SDK supports vendor-agnostic model handoffs, chaining both local and hosted (MCP) tools, and streaming across any provider—all in 5 lines of code. Plus, our cloud infra lets you deploy an MCP server in 3 clicks so anyone can equip their agent with your tools. Let us do the heavy lifting so your agents can fly 🪽 Thank you to our incredible team and our early supporters: Calvin Chin, habib.hajloo from E14 Fund, Yazan El-Baba from Emergence Capital, don stalter from Sunshine Lake, jamestan from Transpose Platform, Liquid 2 Ventures, FPV Ventures, Umesh Khanna 🇨🇦🇺🇸, Ant Wilson — e/postgres, Cal Henderson, Thomas Wolf, Thomas Dohmke, Elad Hazan, Tri Dao
1:47

We just raised an $11M seed to help developers build complex agents across any model and any tool in 5 lines of code. Our round was led by Kindred Ventures (steve jang) and Saga (Max Altman, Ben Braverman, Thomson Nguyen). At Dedalus Labs, we believe the future of AI agents isn’t linear or deterministic. Agents should know when to stop, when to branch, when to reattempt a task, and when to pause and ask for context. As a developer, we make your job simple: define the prompt, select the right tools and guardrails, and let your agent run. We were tired of writing hundreds of lines of code and battling Dockerfiles and infra—all for a spaghetti agent that breaks under stress. With Dedalus, you don’t have to do things the hard way. Our open-source SDK supports vendor-agnostic model handoffs, chaining both local and hosted (MCP) tools, and streaming across any provider—all in 5 lines of code. Plus, our cloud infra lets you deploy an MCP server in 3 clicks so anyone can equip their agent with your tools. Let us do the heavy lifting so your agents can fly 🪽 Thank you to our incredible team and our early supporters: Calvin Chin, habib.hajloo from E14 Fund, Yazan El-Baba from Emergence Capital, don stalter from Sunshine Lake, jamestan from Transpose Platform, Liquid 2 Ventures, FPV Ventures, Umesh Khanna 🇨🇦🇺🇸, Ant Wilson — e/postgres, Cal Henderson, Thomas Wolf, Thomas Dohmke, Elad Hazan, Tri Dao

Cathy Di

1,050,494 次观看 • 9 个月前

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
30:12

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

228,113 次观看 • 3 个月前

Over the past few months at Dedalus Labs, we’ve noticed how many talented founders from around the world are being held back by one thing: location. There is no better place in the world to build an AI startup than San Francisco. SF is home to all the major AI labs, top talent, world-class investors, and it is where the future is being built every day. That’s why, this December, we’re giving builders everywhere a chance to break in. We are taking over and launching Break In—a month-long hacker house program in the heart of San Francisco. If you’re not from SF, and you’re building an AI startup, this is your chance to join us. Build your startup on top of Dedalus’ Agents SDK or MCP deployment infrastructure and we’ll cover your stay (housing, lunch, and co-working space). As a member of Break In, you’ll get access to all the best parts of SF. You’ll be introduced to top founders, mentors, and investors. You’ll get to skip the line at the biggest tech events. Plus, you’ll receive free API credits and expanded access to the best-in-class AI stack through our partner network of top AI infrastructure companies. Applications open October 27th and close November 10th. We will be accepting applications on a rolling basis. Final acceptances will go out November 14th to ensure international founders have enough time to secure visas. Ready to break in? Follow us on Twitter/X for more updates and visit the link in the comments to apply on October 27th!
2:39

Over the past few months at Dedalus Labs, we’ve noticed how many talented founders from around the world are being held back by one thing: location. There is no better place in the world to build an AI startup than San Francisco. SF is home to all the major AI labs, top talent, world-class investors, and it is where the future is being built every day. That’s why, this December, we’re giving builders everywhere a chance to break in. We are taking over and launching Break In—a month-long hacker house program in the heart of San Francisco. If you’re not from SF, and you’re building an AI startup, this is your chance to join us. Build your startup on top of Dedalus’ Agents SDK or MCP deployment infrastructure and we’ll cover your stay (housing, lunch, and co-working space). As a member of Break In, you’ll get access to all the best parts of SF. You’ll be introduced to top founders, mentors, and investors. You’ll get to skip the line at the biggest tech events. Plus, you’ll receive free API credits and expanded access to the best-in-class AI stack through our partner network of top AI infrastructure companies. Applications open October 27th and close November 10th. We will be accepting applications on a rolling basis. Final acceptances will go out November 14th to ensure international founders have enough time to secure visas. Ready to break in? Follow us on Twitter/X for more updates and visit the link in the comments to apply on October 27th!

Cathy Di

105,225 次观看 • 9 个月前

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.
0:33

This Chinese guy created agents in Claude Code for MCP servers and single-handedly serves 6 marketing agencies a month from one iPhone, earning $5,000 from each. Inside he runs a pipeline of 7 agents on Claude Sonnet 4.6 that every Monday pulls a scan of the tech stack from a selected agency, develops an MCP server for its ad accounts, and over the course of a week brings it to production code ready to connect to Claude Desktop. No DevOps, no senior developer, no project manager. Just a Mac Mini in a work corner, an iPhone in the pocket, and a single API key. And traditional dev shops keep 5 people on project rates for the same contract, while his entire P&L is tokens, dirt-cheap hosting on Cloudflare, and Calendly. 7 agents run under a shared orchestrator-router and burn about 5 million tokens a day, which in the API bill comes out to $540 a month. The Mac Mini itself sits at home and keeps the entire orchestrator running 24/7, and from the iPhone the owner connects to it through a secure remote terminal and sees the output of any session right on the smartphone screen, wherever he happens to be. His starting system prompt looks like this: "you run a solo shop for custom MCP servers for marketing agencies. you hand out read-only tasks to 6 sub-agents and own all commits and shipping yourself. sub-agents: // Hunter (finds marketing agencies of 15 to 60 people that have no MCP access to Google Ads, Meta Ads, TikTok Ads, and HubSpot) // Mapper (pulls their tech stack, identifies 3 to 5 integration pains, and simultaneously writes the technical spec for the server: which tools, resources, and prompts to export through MCP, which auth flow and rate limit) // Coder (generates an MCP server in Python through the MCP SDK, deploys 8 to 15 tools for ad accounts and CRM) // Validator (connects the server to Claude Desktop, runs real client API keys in a sandbox, and checks for compliance with the MCP spec) // Shipper (writes a README, integration guide, deployment manual, packages the server, and hosts it on Cloudflare Workers or pushes to the GitHub of the client) // Mobile (always online on the iPhone, books demo calls in Calendly, picks up hot fixes, and confirms contracts through a secure remote terminal to the Mac Mini). only 1 owner agent works on 1 contract, no overlaps. you pull the owner out of observation mode only when a deal goes above $7,500 or the test coverage of the server drops below 85%." This prompt gives the system an understanding of its role and the limits of intervention from the very first line. It knows it is supposed to find agencies on its own. It knows it is supposed to bring every MCP server to production on its own. It knows it connects the live owner only on large deals or when the tests do not converge. → The pipeline runs without breaks, day or night → Hunter goes through about 130 marketing agencies on LinkedIn and Clutch per day → Mapper rolls out 4 audit reports with the tech stack and a final spec for each → Coder writes 1 to 2 MCP servers per week in Python with 8 to 15 tools → Validator validates every server through Claude Desktop with real client API keys → Shipper rolls out the full documentation package and pushes the finished product to Cloudflare Workers or the GitHub of the client And only when a contract breaks $7,500 or test coverage drops below 85% does the orchestrator pull the owner from whatever he is doing. And when the owner at that moment is behind the wheel or at a meeting in a coworking space, the Mobile agent in his iPhone picks up 1 contract in progress: confirms a meeting with the agency CMO in Calendly, opens a live demo of the MCP server through a secure terminal to the Mac Mini, and writes the test result to the shared state. The owner just swipes "approve" and in 15 minutes joins the Zoom demo. The fresh system log from last Wednesday looks like this: "hunter report: 132 agencies checked on LinkedIn and Clutch, 19 without MCP integrations, 8 with active requests for AI tooling in job posts, 4 with an open Q4 budget. passing to mapper." "coder: MCP server for Northwave Performance Marketing built in Python, 11 tools for Google Ads, Meta Ads, and GA4, 320 lines of code. exported to /Users/dev/mcp-shop/clients/northwave/server.py. validator connecting to Claude Desktop." "validator: 11 tools passed validation through Claude Desktop, test coverage 92%, average latency 380 ms. passing to shipper." "eval flag: contract with Pacific Reach Agency at $8,200 exceeds the approved limit of $7,500. sending for manual review." In his work setup there is no cloud server, no external team, and not even a separate office. At home sits a Mac Mini with a sandbox at /Users/dev/mcp-shop, on top runs an MCP router with a single API key to Claude, and the same key is forwarded to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo shop for custom MCP servers for marketing agencies: $540 a month on the API, about $30,000 into the account, and between them 7 system prompts, 1 Mac Mini in a work corner, and 1 iPhone that never leaves the pocket.

Blaze

55,926 次观看 • 2 个月前

The end of coding? *Epic* conversation with Guillermo Rauch of Vercel on vibe coding, MCP, agents and building products in the AI era. (00:00) - Intro: Guillermo's Story (02:08) - What is v0 and Why Did It Take Off So Fast? (04:10) - Building a hit product with < people (07:51) - Cursor, Replit, etc: v0 vs Other AI Coding Tools (10:35) - Everyone can cook - What is Vibe Coding? (17:05) - Is v0 Just Frontend? Moving Toward Full Stack 19:40 - How to Become a Great Vibe Coder (23:35) - A GUI for AI: The Future of Interfaces (29:46) - Developer Love vs Agent Love (33:41) - The Importance of Taste in the AI Era (39:10) - MCP: The Protocol for AI-to-AI Communication (43:11) - Security and the Risks of Agentic Web (45:25) - Are Enterprises Ready for the Agentic Future? (49:42) - Building a Data Flywheel (56:06) - The Vercel AI Cloud: From Pixels to Tokens (1:10:14) - Adapting to a Non-Developer Persona (1:13:47) - Retention, Margins, and the Business of AI (1:16:51) - The Secret Behind Vercel Last Year Growth (1:24:15) - The importance of Online Presence (1:30:49) - Everything, Everywhere, All at Once: Keeping your Sanity as a CEO (1:34:59) - Guillermo's Advice to Younger Self
1:45:40

The end of coding? *Epic* conversation with Guillermo Rauch of Vercel on vibe coding, MCP, agents and building products in the AI era. (00:00) - Intro: Guillermo's Story (02:08) - What is v0 and Why Did It Take Off So Fast? (04:10) - Building a hit product with < people (07:51) - Cursor, Replit, etc: v0 vs Other AI Coding Tools (10:35) - Everyone can cook - What is Vibe Coding? (17:05) - Is v0 Just Frontend? Moving Toward Full Stack 19:40 - How to Become a Great Vibe Coder (23:35) - A GUI for AI: The Future of Interfaces (29:46) - Developer Love vs Agent Love (33:41) - The Importance of Taste in the AI Era (39:10) - MCP: The Protocol for AI-to-AI Communication (43:11) - Security and the Risks of Agentic Web (45:25) - Are Enterprises Ready for the Agentic Future? (49:42) - Building a Data Flywheel (56:06) - The Vercel AI Cloud: From Pixels to Tokens (1:10:14) - Adapting to a Non-Developer Persona (1:13:47) - Retention, Margins, and the Business of AI (1:16:51) - The Secret Behind Vercel Last Year Growth (1:24:15) - The importance of Online Presence (1:30:49) - Everything, Everywhere, All at Once: Keeping your Sanity as a CEO (1:34:59) - Guillermo's Advice to Younger Self

Matt Turck

86,153 次观看 • 1 年前

Real agents will not be limited by models first. They will be limited by data access. Max from Teneo Protocol joins the Acc Podcast to unpack why public web data is getting locked behind walls, and what permissionless infrastructure could unlock for builders, businesses, and the agent economy. Max Full conversation below. 👇 00:00 Intro + what we are covering 01:17 Teneo in one line (elevator pitch) 02:07 Why it matters - users as data owners, not “data lords” 04:06 Max’s origin story + how he got into Web3 05:02 Early days - Ethereum mining, rigs, learnings 05:35 The founding team - 4 co-founders, 8 years together 06:38 The pivot - how Teneo was born 08:19 Product overview - Community Node as the foundation 10:35 Chatroom - the simple UI for specialized agents (private beta) 11:41 SDKs - building on Teneo (customer SDK + agent SDK) 14:17 AI agents era - why real-time data access is the bottleneck 19:27 The core problem - APIs locked down, access gets expensive 22:36 What Max does day to day as CEO 26:28 How to start with Teneo - beginner to advanced paths 30:08 Lessons from pivots + building with the right team 33:08 Ops advice - trust and the right people 35:16 2-10 year landscape - data pipelines, cost barriers, opportunity 37:26 What’s live now + how people contribute today 38:50 Agent SDK launch - early feedback and traction 39:56 Next 6-12 months - pushing more open source 42:36 Awareness + surprising use cases (example: government PDFs) 46:00 Speed, latency, and agent-to-agent payments (microtransactions) 48:38 Web3 adoption - users won’t notice, it just needs to work 51:07 What’s next + closing thoughts + where to get involved
50:36

Real agents will not be limited by models first. They will be limited by data access. Max from Teneo Protocol joins the Acc Podcast to unpack why public web data is getting locked behind walls, and what permissionless infrastructure could unlock for builders, businesses, and the agent economy. Max Full conversation below. 👇 00:00 Intro + what we are covering 01:17 Teneo in one line (elevator pitch) 02:07 Why it matters - users as data owners, not “data lords” 04:06 Max’s origin story + how he got into Web3 05:02 Early days - Ethereum mining, rigs, learnings 05:35 The founding team - 4 co-founders, 8 years together 06:38 The pivot - how Teneo was born 08:19 Product overview - Community Node as the foundation 10:35 Chatroom - the simple UI for specialized agents (private beta) 11:41 SDKs - building on Teneo (customer SDK + agent SDK) 14:17 AI agents era - why real-time data access is the bottleneck 19:27 The core problem - APIs locked down, access gets expensive 22:36 What Max does day to day as CEO 26:28 How to start with Teneo - beginner to advanced paths 30:08 Lessons from pivots + building with the right team 33:08 Ops advice - trust and the right people 35:16 2-10 year landscape - data pipelines, cost barriers, opportunity 37:26 What’s live now + how people contribute today 38:50 Agent SDK launch - early feedback and traction 39:56 Next 6-12 months - pushing more open source 42:36 Awareness + surprising use cases (example: government PDFs) 46:00 Speed, latency, and agent-to-agent payments (microtransactions) 48:38 Web3 adoption - users won’t notice, it just needs to work 51:07 What’s next + closing thoughts + where to get involved

Acc Ventures

43,976 次观看 • 7 个月前

🚨 New Proof of Vision out today folks! In this 34th PoV episode, our Director of Protocol Services, Kirk had on Andrew Hill, Co-Founder and CEO of Recall When it comes to your business, you’d never trust someone without a proven track record to make high-risk decisions So why should it be any different with AI agents? How do you know today which AI agents you should trust? AI agents are multiplying at unprecedented scale, with millions designed to shape the way we work, make decisions, and live our lives But how can we trust them? The challenge is trust: as dependence on these agents increases, so too does the exponential risk and cost of delegating to the wrong one This is the core challenge of reputation: the need for a transparent system that proves what AI agents can do, where they excel, and which will succeed That’s the reason why Recall exists Recall is the infrastructure protocol to discover, verify, and rank AI agents in real time, rewarding the best through on-chain competitions that begin with trading PnL and expand to any measurable task, from research to healthcare to business strategy In this episode, Andrew breaks down Recall’s mission, the problem it solves, how Agent Rank works, strategies to attract agents and users, the role of community, and the long-term vision plus much more Enjoy the Podcast 👇 ⏲ Timestamps: 00:00 - Intro 01:50 - Andrew’s journey into crypto and AI 05:00 - What problem is Recall solving? 10:00 - Agent Rank: how Recall actually ranks agents 16:03 - How Recall is attracting AI agents to compete? 19:10 - How big the community is today and the role it plays in giving builders real feedback 22:49 - How Recall ensures transparency and trust in its rankings 25:14 - Why users join Recall competitions 27:20 - Product-market fit and distribution 31:15 - What competitions could look like outside trading and what new use cases Recall is exploring 34:46 - What AI can’t replace 38:40 - The limits of AI in human interaction 40:37 - The long-term vision for Recall 40:40 - Is Recall built more for individual users, or is it more of a B2B service? 43:48 - Recall Business Model 44:42 - Closing thoughts and what’s next for Recall
46:16

🚨 New Proof of Vision out today folks! In this 34th PoV episode, our Director of Protocol Services, Kirk had on Andrew Hill, Co-Founder and CEO of Recall When it comes to your business, you’d never trust someone without a proven track record to make high-risk decisions So why should it be any different with AI agents? How do you know today which AI agents you should trust? AI agents are multiplying at unprecedented scale, with millions designed to shape the way we work, make decisions, and live our lives But how can we trust them? The challenge is trust: as dependence on these agents increases, so too does the exponential risk and cost of delegating to the wrong one This is the core challenge of reputation: the need for a transparent system that proves what AI agents can do, where they excel, and which will succeed That’s the reason why Recall exists Recall is the infrastructure protocol to discover, verify, and rank AI agents in real time, rewarding the best through on-chain competitions that begin with trading PnL and expand to any measurable task, from research to healthcare to business strategy In this episode, Andrew breaks down Recall’s mission, the problem it solves, how Agent Rank works, strategies to attract agents and users, the role of community, and the long-term vision plus much more Enjoy the Podcast 👇 ⏲ Timestamps: 00:00 - Intro 01:50 - Andrew’s journey into crypto and AI 05:00 - What problem is Recall solving? 10:00 - Agent Rank: how Recall actually ranks agents 16:03 - How Recall is attracting AI agents to compete? 19:10 - How big the community is today and the role it plays in giving builders real feedback 22:49 - How Recall ensures transparency and trust in its rankings 25:14 - Why users join Recall competitions 27:20 - Product-market fit and distribution 31:15 - What competitions could look like outside trading and what new use cases Recall is exploring 34:46 - What AI can’t replace 38:40 - The limits of AI in human interaction 40:37 - The long-term vision for Recall 40:40 - Is Recall built more for individual users, or is it more of a B2B service? 43:48 - Recall Business Model 44:42 - Closing thoughts and what’s next for Recall

Alea Research

19,677 次观看 • 10 个月前

⚫UNCANNY VALLEY: PERPLEXITY VS GOOGLE — THE WAR FOR THE FUTURE OF SEARCH BEGINS Special Guest: Aravind Srinivas Host: Dr Danish Search is dead. Agents are rising. Phones are getting smarter—without Apple or Google. Aravind Srinivas, CEO of Perplexity, lays out the future: AI-native assistants, ambient search, agent browsers, and a war for the next-gen OS. If Google is the old internet—Perplexity wants to be the new one. Welcome to The Uncanny Valley Weekly Series, Fridays at 4:20 PM ET, ONLY on 𝕏. Episode 5: THE AGENT ERA IS HERE — AND GOOGLE CAN’T STOP IT 01:05 – “We started as an answer engine.” How Perplexity went from RAG to research to real-world action. 03:03 – “Tell me what I should think about NVIDIA.” Agents as consultants, not just search engines. 05:07 – Buy buttons, autofill, AI shopping carts—how agents are already doing tasks. 07:05 – “You don’t have to see the tabs.” What the new browser will look like. 10:45 – “Warren Buffett doesn’t use apps—why should you?” The inspiration behind the AI-native phone. 12:36 – Why Apple, Google, and even OpenAI won’t build an AI-native OS. 17:28 – “Search is the most important tool in the agent era.” And Perplexity owns it. 21:33 – Mukesh Ambani’s advice: “Content is king, but distribution is GOD.” 27:13 – “Retrofit AI into iOS? It’ll never work.” Why the future needs a native platform. 30:26 – Humane failed, but the idea didn’t. Why assistants—not apps—are the next big UX shift. 33:38 – “We want Perplexity to feel like Apple.” Design still matters—even with agents. 37:11 – Why the real moat in AI isn’t models—it’s trust, taste, and vibe. 42:07 – 80M impressions in 6 weeks: How “Ask Perplexity” is going viral on 𝕏. 47:52 – “We’ve survived the internet—AI’s not scarier.” Aravind pushes back on the doomerism. 50:00 – Healthcare, finance, travel—Perplexity wants to power the vertical agent revolution. 54:24 – “LLMs can reason. But only agents can do.” Why execution is the next AI frontier. 56:34 – COMET browser drops in 3 weeks.
57:05

⚫UNCANNY VALLEY: PERPLEXITY VS GOOGLE — THE WAR FOR THE FUTURE OF SEARCH BEGINS Special Guest: Aravind Srinivas Host: Dr Danish Search is dead. Agents are rising. Phones are getting smarter—without Apple or Google. Aravind Srinivas, CEO of Perplexity, lays out the future: AI-native assistants, ambient search, agent browsers, and a war for the next-gen OS. If Google is the old internet—Perplexity wants to be the new one. Welcome to The Uncanny Valley Weekly Series, Fridays at 4:20 PM ET, ONLY on 𝕏. Episode 5: THE AGENT ERA IS HERE — AND GOOGLE CAN’T STOP IT 01:05 – “We started as an answer engine.” How Perplexity went from RAG to research to real-world action. 03:03 – “Tell me what I should think about NVIDIA.” Agents as consultants, not just search engines. 05:07 – Buy buttons, autofill, AI shopping carts—how agents are already doing tasks. 07:05 – “You don’t have to see the tabs.” What the new browser will look like. 10:45 – “Warren Buffett doesn’t use apps—why should you?” The inspiration behind the AI-native phone. 12:36 – Why Apple, Google, and even OpenAI won’t build an AI-native OS. 17:28 – “Search is the most important tool in the agent era.” And Perplexity owns it. 21:33 – Mukesh Ambani’s advice: “Content is king, but distribution is GOD.” 27:13 – “Retrofit AI into iOS? It’ll never work.” Why the future needs a native platform. 30:26 – Humane failed, but the idea didn’t. Why assistants—not apps—are the next big UX shift. 33:38 – “We want Perplexity to feel like Apple.” Design still matters—even with agents. 37:11 – Why the real moat in AI isn’t models—it’s trust, taste, and vibe. 42:07 – 80M impressions in 6 weeks: How “Ask Perplexity” is going viral on 𝕏. 47:52 – “We’ve survived the internet—AI’s not scarier.” Aravind pushes back on the doomerism. 50:00 – Healthcare, finance, travel—Perplexity wants to power the vertical agent revolution. 54:24 – “LLMs can reason. But only agents can do.” Why execution is the next AI frontier. 56:34 – COMET browser drops in 3 weeks.

Mario Nawfal

1,748,592 次观看 • 1 年前

Supabase (YC S20) is one of the fastest-growing developer platforms in the world, with more than 10 million developers using it. As AI coding agents like Claude Code, Lovable, Bolt, and Codex have taken off, they've become the backend powering millions of AI-generated apps. At Startup School Paris, Supabase co-founder and CEO Paul Copplestone (Paul Copplestone - e/postgres) sat down with YC's Nicolas Dessaigne to discuss why AI coding agents have changed the way developers build software, how open source helped Supabase compete with the cloud giants, and why the next frontier is self-driving databases. 00:56 — Paul's Origin Story 02:13 — Two Failed Startups First 04:12 — Why Postgres? Why Open Source? 07:11 — The Pivot That Actually Worked 08:03 — Targeting YC Startups from Day One 09:45 — Fully Open Source — The Risky Choice 12:04 — Winning Developer Trust 13:33 — Time to Value: 8 Minutes → 5 Seconds 15:45 — The AI Second Life Begins 17:48 — Supabase for Platforms 19:09 — Everything Going Up Into the Right 20:44 — When Agents Became the Users 22:26 — Advice for Founders Building Dev Tools Today 23:47 — Why Open Source Won the LLM Era 25:32 — $500M Round, $10B Valuation 26:01 — What Keeps a Founder Grounded 28:31 — 360 People, 60 Countries, Zero Offices
31:20

Supabase (YC S20) is one of the fastest-growing developer platforms in the world, with more than 10 million developers using it. As AI coding agents like Claude Code, Lovable, Bolt, and Codex have taken off, they've become the backend powering millions of AI-generated apps. At Startup School Paris, Supabase co-founder and CEO Paul Copplestone (Paul Copplestone - e/postgres) sat down with YC's Nicolas Dessaigne to discuss why AI coding agents have changed the way developers build software, how open source helped Supabase compete with the cloud giants, and why the next frontier is self-driving databases. 00:56 — Paul's Origin Story 02:13 — Two Failed Startups First 04:12 — Why Postgres? Why Open Source? 07:11 — The Pivot That Actually Worked 08:03 — Targeting YC Startups from Day One 09:45 — Fully Open Source — The Risky Choice 12:04 — Winning Developer Trust 13:33 — Time to Value: 8 Minutes → 5 Seconds 15:45 — The AI Second Life Begins 17:48 — Supabase for Platforms 19:09 — Everything Going Up Into the Right 20:44 — When Agents Became the Users 22:26 — Advice for Founders Building Dev Tools Today 23:47 — Why Open Source Won the LLM Era 25:32 — $500M Round, $10B Valuation 26:01 — What Keeps a Founder Grounded 28:31 — 360 People, 60 Countries, Zero Offices

Y Combinator

53,449 次观看 • 4 天前

AI INTERVIEW: OPENAI'S SECRET WEAPON AI agents are no longer just hype—they're here to revolutionize automation, Web3, and beyond. SwarmNode.ai is building a serverless AI agent platform for scalability, efficiency, and real-world impact. In this exclusive interview, he reveals how AI swarms can outperform single models, why OpenAI’s Operator is just the beginning, and how crypto is fueling AI innovation. Plus, he breaks down DeepSeek’s game-changing AI breakthrough, the future of agent monetization, and why serverless AI could be the next frontier in automation. 01:37 – From Engineering to AI: The journey into artificial intelligence. 02:43 – The GPT-3 Moment: How OpenAI’s tech pulled him in. 04:10 – AI’s Biggest Challenge: Why real-world use cases lag behind. 05:05 – OpenAI’s Operator: Why it’s “rudimentary” (for now). 06:25 – Crypto & AI: How tokens help bootstrap AI startups. 08:15 – Can You Bootstrap a Startup with a Token? The trade-offs. 09:56 – 90% of AI Token Holders Don’t Use the Product—Does It Matter? 11:18 – What is SwarmNode?: AI agents, hosted serverlessly. 14:23 – AI Swarms: Why multiple agents outperform single models. 16:08 – What is a Swarm? A simple definition of collaborative AI. 17:32 – “How Can I Make Money with AI?”: Real-world use cases. 18:41 – AI Bounties: Hiring devs to build your custom agent. 20:50 – The Future of AI Marketplaces: Monetizing pre-built agents. 23:15 – DeepSeek’s Disruption: Why it’s good news for AI. 24:46 – Is SwarmNode Compatible with DeepSeek? How it integrates. 26:17 – SwarmNode vs. AI Launchpads: What makes it different? 27:42 – Why Serverless Matters: Cost savings & efficiency. 29:53 – AI Agents in the Real World: Booking flights, managing workflows, and more. 31:11 – Building SwarmNode for Developers: Why it started as a personal project. 32:27 – Explosive Growth: 200,000 AI agent executions in 5 weeks. 34:41 – Why SwarmNode Agents Aren’t Visible on 𝕏 Yet. 36:46 – Startup Hiring Lessons: Finding top AI talent. 39:15 – Why SwarmNode is Built in Python (and What’s Next). 40:32 – Scaling AI Workloads: Handling traffic surges. 41:42 – AWS & Cost Challenges: The biggest monetization hurdle. 42:58 – 2025: The Year of Mass AI Adoption. 45:22 – Should We Be Worried About AI’s Rapid Growth? 46:46 – The Most Underrated AI Tools Right Now. 47:34 – What’s Next for SwarmNode?: Making AI accessible to everyone.
49:12

AI INTERVIEW: OPENAI'S SECRET WEAPON AI agents are no longer just hype—they're here to revolutionize automation, Web3, and beyond. SwarmNode.ai is building a serverless AI agent platform for scalability, efficiency, and real-world impact. In this exclusive interview, he reveals how AI swarms can outperform single models, why OpenAI’s Operator is just the beginning, and how crypto is fueling AI innovation. Plus, he breaks down DeepSeek’s game-changing AI breakthrough, the future of agent monetization, and why serverless AI could be the next frontier in automation. 01:37 – From Engineering to AI: The journey into artificial intelligence. 02:43 – The GPT-3 Moment: How OpenAI’s tech pulled him in. 04:10 – AI’s Biggest Challenge: Why real-world use cases lag behind. 05:05 – OpenAI’s Operator: Why it’s “rudimentary” (for now). 06:25 – Crypto & AI: How tokens help bootstrap AI startups. 08:15 – Can You Bootstrap a Startup with a Token? The trade-offs. 09:56 – 90% of AI Token Holders Don’t Use the Product—Does It Matter? 11:18 – What is SwarmNode?: AI agents, hosted serverlessly. 14:23 – AI Swarms: Why multiple agents outperform single models. 16:08 – What is a Swarm? A simple definition of collaborative AI. 17:32 – “How Can I Make Money with AI?”: Real-world use cases. 18:41 – AI Bounties: Hiring devs to build your custom agent. 20:50 – The Future of AI Marketplaces: Monetizing pre-built agents. 23:15 – DeepSeek’s Disruption: Why it’s good news for AI. 24:46 – Is SwarmNode Compatible with DeepSeek? How it integrates. 26:17 – SwarmNode vs. AI Launchpads: What makes it different? 27:42 – Why Serverless Matters: Cost savings & efficiency. 29:53 – AI Agents in the Real World: Booking flights, managing workflows, and more. 31:11 – Building SwarmNode for Developers: Why it started as a personal project. 32:27 – Explosive Growth: 200,000 AI agent executions in 5 weeks. 34:41 – Why SwarmNode Agents Aren’t Visible on 𝕏 Yet. 36:46 – Startup Hiring Lessons: Finding top AI talent. 39:15 – Why SwarmNode is Built in Python (and What’s Next). 40:32 – Scaling AI Workloads: Handling traffic surges. 41:42 – AWS & Cost Challenges: The biggest monetization hurdle. 42:58 – 2025: The Year of Mass AI Adoption. 45:22 – Should We Be Worried About AI’s Rapid Growth? 46:46 – The Most Underrated AI Tools Right Now. 47:34 – What’s Next for SwarmNode?: Making AI accessible to everyone.

Mario Nawfal

338,236 次观看 • 1 年前

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code
1:00:16

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Matt Turck

82,161 次观看 • 11 个月前

In this livestream I break down the OpenClaw AI agent narrative from the operator’s perspective: what it actually is, why it’s different from ChatGPT/Grok/Claude Code, and why “it’s just automation” misses the real shift. We cover the practical unlocks (local execution, persistent memory, computer-use + browser control, reusable skills/plugins) and why this design pattern can replace a lot of expensive SaaS workflows over time. Then I zoom out to the crypto angle: why the market will mint endless OpenClaw “slop” coins, how I think about separating infra from hype, and the two names I’m watching (BNKR + CLAWD). 00:00 Why the OpenClaw AI agent narrative is bigger than you think 00:39 Two-part video: OpenClaw productivity first, crypto narrative second 01:30 What OpenClaw is (an AI agent framework, not a chatbot) 01:44 Why ChatGPT, Grok, and Claude Code are still useful but incomplete 03:19 OpenClaw vs n8n and Zapier for automation 05:03 Why Zapier pricing breaks real businesses 06:07 Why running locally matters (any app, any chat platform) 07:56 Persistent memory: how agents learn your style over time 09:55 Computer-use agents: browser control and no-API workflows 11:27 Skills and plugins: reusable workflows that self-improve 13:52 The simple setup and why model choice is flexible 16:05 Cross-platform ops: Telegram, Slack, Discord, and email in one brain 20:52 Why AI SaaS tools get replaced by agent-built workflows 25:37 What this is not: no AGI, no “sentient” coin story 29:55 How to approach the OpenClaw coin wave (infra over slop) 32:43 BNKR and CLAWD: my two picks for exposure to the narrative
44:45

In this livestream I break down the OpenClaw AI agent narrative from the operator’s perspective: what it actually is, why it’s different from ChatGPT/Grok/Claude Code, and why “it’s just automation” misses the real shift. We cover the practical unlocks (local execution, persistent memory, computer-use + browser control, reusable skills/plugins) and why this design pattern can replace a lot of expensive SaaS workflows over time. Then I zoom out to the crypto angle: why the market will mint endless OpenClaw “slop” coins, how I think about separating infra from hype, and the two names I’m watching (BNKR + CLAWD). 00:00 Why the OpenClaw AI agent narrative is bigger than you think 00:39 Two-part video: OpenClaw productivity first, crypto narrative second 01:30 What OpenClaw is (an AI agent framework, not a chatbot) 01:44 Why ChatGPT, Grok, and Claude Code are still useful but incomplete 03:19 OpenClaw vs n8n and Zapier for automation 05:03 Why Zapier pricing breaks real businesses 06:07 Why running locally matters (any app, any chat platform) 07:56 Persistent memory: how agents learn your style over time 09:55 Computer-use agents: browser control and no-API workflows 11:27 Skills and plugins: reusable workflows that self-improve 13:52 The simple setup and why model choice is flexible 16:05 Cross-platform ops: Telegram, Slack, Discord, and email in one brain 20:52 Why AI SaaS tools get replaced by agent-built workflows 25:37 What this is not: no AGI, no “sentient” coin story 29:55 How to approach the OpenClaw coin wave (infra over slop) 32:43 BNKR and CLAWD: my two picks for exposure to the narrative

VirtualBacon

21,557 次观看 • 5 个月前

SaaS isn’t dead, it just needs to become agent-native. Linear (Linear) is a great example of how: They pivoted the product to be used by both humans and agents, and that has made them one of the premier software tools in the agent-native era. I had Linear’s cofounder and CEO Karri Saarinen on Every 📧's AI & I to talk about how a product management tool for human software developers became an agent-native tool—and how Linear’s trajectory reveals a bright future for SaaS businesses: - Speed means decisions matter more, not less. AI makes it easy to have an idea and build it without considering whether its existence is justified. When ChatGPT was released, SaaS companies were launching their own chatbots left, right, and center. Instead of jumping on the bandwagon, Linear stopped to consider whether the application was useful. (It wasn’t.) - Just because the technology has changed doesn’t mean your mission should. Karri attributes Linear’s success to never losing sight of what matters: helping teams develop great software. Instead of chasing trends, Linear focused on understanding how AI was impacting its customers’ workflows—and updating its product accordingly. - Agents are now first-class users. Linear never tried to change what it was or did well; it just expanded the user base. Companies can now kick off agents inside Linear, manage them, and track what they're working on alongside the humans on the team, which explains why Codex, Coinbase, and Brex all run their agents on Linear. This is a must watch for anyone interested in how an agent-native SaaS company operates. Watch below! Timestamps: Introduction and how Every first discovered Linear: 00:00:39 Why Linear waited to ship AI features instead of rushing to chatbots: 00:02:00 Linear's agent platform and becoming the system that guides AI agents: 00:05:06 Why "SaaS is dead" is a simplistic narrative: 00:07:42 How Linear adopted AI coding tools internally: 00:12:18 AI's impact on product building workflows—speed versus thoughtfulness: 00:17:45 The value of conceptual work and thinking before shipping: 00:22:18 How AI is reshaping Linear's product strategy: 00:29:30 Demo: Linear's agent skills, shared context, and code review workflow: 00:37:18 The future of product development and the enduring role of human judgment: 00:47:48
52:48

SaaS isn’t dead, it just needs to become agent-native. Linear (Linear) is a great example of how: They pivoted the product to be used by both humans and agents, and that has made them one of the premier software tools in the agent-native era. I had Linear’s cofounder and CEO Karri Saarinen on Every 📧's AI & I to talk about how a product management tool for human software developers became an agent-native tool—and how Linear’s trajectory reveals a bright future for SaaS businesses: - Speed means decisions matter more, not less. AI makes it easy to have an idea and build it without considering whether its existence is justified. When ChatGPT was released, SaaS companies were launching their own chatbots left, right, and center. Instead of jumping on the bandwagon, Linear stopped to consider whether the application was useful. (It wasn’t.) - Just because the technology has changed doesn’t mean your mission should. Karri attributes Linear’s success to never losing sight of what matters: helping teams develop great software. Instead of chasing trends, Linear focused on understanding how AI was impacting its customers’ workflows—and updating its product accordingly. - Agents are now first-class users. Linear never tried to change what it was or did well; it just expanded the user base. Companies can now kick off agents inside Linear, manage them, and track what they're working on alongside the humans on the team, which explains why Codex, Coinbase, and Brex all run their agents on Linear. This is a must watch for anyone interested in how an agent-native SaaS company operates. Watch below! Timestamps: Introduction and how Every first discovered Linear: 00:00:39 Why Linear waited to ship AI features instead of rushing to chatbots: 00:02:00 Linear's agent platform and becoming the system that guides AI agents: 00:05:06 Why "SaaS is dead" is a simplistic narrative: 00:07:42 How Linear adopted AI coding tools internally: 00:12:18 AI's impact on product building workflows—speed versus thoughtfulness: 00:17:45 The value of conceptual work and thinking before shipping: 00:22:18 How AI is reshaping Linear's product strategy: 00:29:30 Demo: Linear's agent skills, shared context, and code review workflow: 00:37:18 The future of product development and the enduring role of human judgment: 00:47:48

Dan Shipper 📧

36,359 次观看 • 3 个月前

BREAKING: Merge Launches ‘Agent Handler’ Control AI Access, Tokenmaxxed $$$ Bills, & Stop Mass Data Leaks "We don't trust agents" "The second you connect it to tools, that's where everything goes wrong." OpenAI. Perplexity. Netflix. Uber. Mistral. Dropbox. JPMorgan.. all quietly run on Merge Co-Founders CEO Shensi Ding Ding & CTO Gil Feig dive into it all We cover: - MASSIVE AI Security scares are just starting - Tokenmaxxing bills - Agent Handler - Gateway routing - Winning enterprise logos - The SaaSpocalypse 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Shensi Ding & Gil Feig, Co-Founders at Merge (01:04) Three products. One big bet (03:20) How Merge made the AI pivot (04:42) The Classic Innovator’s Dilemma (05:58) Building culture around AI (07:10) The leverage nobody’s talking about (08:52) Codex vs Claude Code (09:15) The scale nobody knew about (09:47) SaaS, Finance, and the Biggest AI Labs (10:46) Why AI companies buy differently (12:04) What AI sales actually looks like (13:04) The Fastest sales cycles in the market (14:35) Why is Cybersecurity broken (15:59) Merge's solution to agent security (19:16) Mythos, Wiz, and the GitHub Hack (22:34) 1,000 Bot signups in one hour (23:23) Real reason companies pay ransom to hackers (25:43) The State of AI Infrastructure Costs (26:41) Internal AI Governance is the next big problem (29:28) Most Popular Integrations on Merge (30:54) Big Giants are planning big moves (31:54) What does Salesforce going headless exactly mean (33:41) Agents don’t need a UI anymore (36:59) Can this AI generation actually adapt (38:25) What Merge looks for in talent (41:25) The SaaSpocalypse is real (45:03) Are AI valuations actually insane? (47:11) How Merge landed OpenAI, Perplexity, Netflix & Uber (49:02) The Metrics that actually drive the business (49:58) Biggest misconceptions in tech right now (51:55) The market is finally catching up to Merge
55:05

BREAKING: Merge Launches ‘Agent Handler’ Control AI Access, Tokenmaxxed $$$ Bills, & Stop Mass Data Leaks "We don't trust agents" "The second you connect it to tools, that's where everything goes wrong." OpenAI. Perplexity. Netflix. Uber. Mistral. Dropbox. JPMorgan.. all quietly run on Merge Co-Founders CEO Shensi Ding Ding & CTO Gil Feig dive into it all We cover: - MASSIVE AI Security scares are just starting - Tokenmaxxing bills - Agent Handler - Gateway routing - Winning enterprise logos - The SaaSpocalypse 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Shensi Ding & Gil Feig, Co-Founders at Merge (01:04) Three products. One big bet (03:20) How Merge made the AI pivot (04:42) The Classic Innovator’s Dilemma (05:58) Building culture around AI (07:10) The leverage nobody’s talking about (08:52) Codex vs Claude Code (09:15) The scale nobody knew about (09:47) SaaS, Finance, and the Biggest AI Labs (10:46) Why AI companies buy differently (12:04) What AI sales actually looks like (13:04) The Fastest sales cycles in the market (14:35) Why is Cybersecurity broken (15:59) Merge's solution to agent security (19:16) Mythos, Wiz, and the GitHub Hack (22:34) 1,000 Bot signups in one hour (23:23) Real reason companies pay ransom to hackers (25:43) The State of AI Infrastructure Costs (26:41) Internal AI Governance is the next big problem (29:28) Most Popular Integrations on Merge (30:54) Big Giants are planning big moves (31:54) What does Salesforce going headless exactly mean (33:41) Agents don’t need a UI anymore (36:59) Can this AI generation actually adapt (38:25) What Merge looks for in talent (41:25) The SaaSpocalypse is real (45:03) Are AI valuations actually insane? (47:11) How Merge landed OpenAI, Perplexity, Netflix & Uber (49:02) The Metrics that actually drive the business (49:58) Biggest misconceptions in tech right now (51:55) The market is finally catching up to Merge

Molly O’Shea

111,346 次观看 • 1 个月前

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:
22:53

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Akshay 🚀

45,815 次观看 • 19 天前

My full interview with Roman Chernin, Co-founder & Chief Business Officer of Nebius Nebius just signed a $17 billion deal with Microsoft and a $3 billion deal with Meta. These are two of the biggest tech companies on Earth - and they're coming to Nebius for AI infrastructure. But the company does so much more than that: - Full-stack AI cloud (data centers → software → managed services) - Nebius Token Factory Nebius Token Factory for managed inference & post-training - Partners include Shopify, Higgsfield, Jetbrains My 5 takeaways with Roman Chernin below - thanks for the conversation! Full interview also available on YT ⬇️ Timestamps: 00:00 - Introduction 01:47 - Overview of Nebius $NBIS 03:23 - Roman's background and role at Nebius 04:10 - The $17B Microsoft & $3B Meta deals 05:29 - Why hyperscalers trust Nebius over building in-house 07:06 - Nebius's full-stack approach: Data centers to managed services 08:39 - Customer segmentation: Hyperscalers & Frontier AI Labs vs AI Startups vs Enterprises 14:41 - Token Factory explained: Managed inference & post-training 17:41 - When to switch from closed-source to open-source models 20:59 - Real results: Process achieves 26% cost reduction 25:05 - Why developers love building on Nebius 28:40 - AI agents and the future of infrastructure interaction 32:22 - NVIDIA's Groq acquisition: What it means for inference 35:38 - Why AI adoption will surprise us
39:46

My full interview with Roman Chernin, Co-founder & Chief Business Officer of Nebius Nebius just signed a $17 billion deal with Microsoft and a $3 billion deal with Meta. These are two of the biggest tech companies on Earth - and they're coming to Nebius for AI infrastructure. But the company does so much more than that: - Full-stack AI cloud (data centers → software → managed services) - Nebius Token Factory Nebius Token Factory for managed inference & post-training - Partners include Shopify, Higgsfield, Jetbrains My 5 takeaways with Roman Chernin below - thanks for the conversation! Full interview also available on YT ⬇️ Timestamps: 00:00 - Introduction 01:47 - Overview of Nebius $NBIS 03:23 - Roman's background and role at Nebius 04:10 - The $17B Microsoft & $3B Meta deals 05:29 - Why hyperscalers trust Nebius over building in-house 07:06 - Nebius's full-stack approach: Data centers to managed services 08:39 - Customer segmentation: Hyperscalers & Frontier AI Labs vs AI Startups vs Enterprises 14:41 - Token Factory explained: Managed inference & post-training 17:41 - When to switch from closed-source to open-source models 20:59 - Real results: Process achieves 26% cost reduction 25:05 - Why developers love building on Nebius 28:40 - AI agents and the future of infrastructure interaction 32:22 - NVIDIA's Groq acquisition: What it means for inference 35:38 - Why AI adoption will surprise us

Elliot Garreffa

29,384 次观看 • 5 个月前

Alright, this one’s worth your attention if you’re building or deploying agents. Future AGI just open-sourced their entire platform and i don’t mean a trimmed-down version. this is the full stack: UI, backend, simulation engine, evals, optimization loop, observability, guardrails, gateway, docs. all in one repo. Apache 2.0. I’ve been putting it through its paces on production agents, and what stands out isn’t just the breadth it’s the architecture. Most of the current “agent reliability” stack is fragmented. tracing lives in one tool, evals in another, guardrails somewhere else. you end up manually connecting dots, and the agent itself doesn’t really improve you just keep patching prompts and hoping for the best. This flips that model. It’s built as a closed feedback loop: simulate failures → evaluate in real time → detect production issues → learn from them → generate fixes → validate against real traffic → check regressions → redeploy → monitor again And when something new breaks, the loop just runs again. no manual glue. The simulation piece is especially strong. instead of static test cases, it generates adversarial, multi-turn conversations based on how your agent actually behaves basically hunting for the exact scenarios where your system fails confidently. ran a few thousand simulations on our side… caught things we definitely would’ve missed. Evals run fast (sub-50ms) across modalities. not LLM-as-judge trained classifiers. guardrails are built-in, not layered on top. observability gives you step-level visibility into reasoning, cost, latency, quality. But the real shift is the optimization loop. Most tools tell you *what* broke. this system actually fixes it, validates the fix, and ensures nothing else regresses. That’s the missing layer. It’s clearly built with production in mind not a research demo. and the fact that it’s self-hostable makes it even more relevant if you’re running serious workloads. If you’ve been duct-taping together infra around your agents, this is probably the closest thing to a unified system i’ve seen so far. Worth checking out. If you're serious about deploying reliable AI agents, this is worth a look: 👉 You can also try it instantly (no setup) via their cloud version:
2:20

Alright, this one’s worth your attention if you’re building or deploying agents. Future AGI just open-sourced their entire platform and i don’t mean a trimmed-down version. this is the full stack: UI, backend, simulation engine, evals, optimization loop, observability, guardrails, gateway, docs. all in one repo. Apache 2.0. I’ve been putting it through its paces on production agents, and what stands out isn’t just the breadth it’s the architecture. Most of the current “agent reliability” stack is fragmented. tracing lives in one tool, evals in another, guardrails somewhere else. you end up manually connecting dots, and the agent itself doesn’t really improve you just keep patching prompts and hoping for the best. This flips that model. It’s built as a closed feedback loop: simulate failures → evaluate in real time → detect production issues → learn from them → generate fixes → validate against real traffic → check regressions → redeploy → monitor again And when something new breaks, the loop just runs again. no manual glue. The simulation piece is especially strong. instead of static test cases, it generates adversarial, multi-turn conversations based on how your agent actually behaves basically hunting for the exact scenarios where your system fails confidently. ran a few thousand simulations on our side… caught things we definitely would’ve missed. Evals run fast (sub-50ms) across modalities. not LLM-as-judge trained classifiers. guardrails are built-in, not layered on top. observability gives you step-level visibility into reasoning, cost, latency, quality. But the real shift is the optimization loop. Most tools tell you *what* broke. this system actually fixes it, validates the fix, and ensures nothing else regresses. That’s the missing layer. It’s clearly built with production in mind not a research demo. and the fact that it’s self-hostable makes it even more relevant if you’re running serious workloads. If you’ve been duct-taping together infra around your agents, this is probably the closest thing to a unified system i’ve seen so far. Worth checking out. If you're serious about deploying reliable AI agents, this is worth a look: 👉 You can also try it instantly (no setup) via their cloud version:

Aakash Verma

22,889 次观看 • 3 个月前

"We were go-karting and doing quite well. Now we've moved to Formula 1, and we're in the middle of the pack. We have a shot at the podium but we have to rewire for the race we're in." Akshay Kothari (Akshay Kothari). Cofounder and COO of Notion. Three years from now, most pre-AI companies will be gone. Notion will be one of the few standing stronger than before. This episode is a field study in how they're pulling it off. Knuckle Up ↓ 00:00 Intro 01:27 What were Notion's core founding principles? 06:20 Which early cultural principles scaled, and which broke? 08:22 How did Notion hire its first employees, and where did they come from? 11:48 How does hiring work now that the founders can't meet everyone? 14:35 Why does Akshay, as COO, prefer to have zero direct reports? 19:05 How do Ivan, Simon, and Akshay divide the work? 21:07 Does Notion's intentionality ever conflict with speed? 25:25 What should other founders steal from Notion's culture? 28:11 When did AI become a reason to rethink the whole product? 30:44 Why were the early AI years a "swamp of despair"? 36:05 How do you push AI across a huge product without losing the user? 39:25 Does Notion buy its AI DNA or build it? 40:44 Should Notion be afraid of OpenAI, Anthropic, and fast copycats? 46:58 What's hardest about the reinvention, and what does "meet the LLM" mean? 52:42 Is Notion AI-native in every function yet? 54:36 Are Notion's engineers still writing code, and how has engineering changed? 1:01:07 Once building is cheap, what's the new bottleneck? 1:02:39 How is AI reshaping sales, marketing, and support? 1:09:07 How many agents run inside Notion, and who builds them? 1:11:28 How has recruiting changed for the AI era? 1:13:48 What still worries Akshay about Notion's future? 1:15:22 Quickfire: admired founders, books, overrated AI advice, and Akshay’s superpower 1:19:42 What should a $50M pre-AI company do in the next 90 days?
1:22:10

"We were go-karting and doing quite well. Now we've moved to Formula 1, and we're in the middle of the pack. We have a shot at the podium but we have to rewire for the race we're in." Akshay Kothari (Akshay Kothari). Cofounder and COO of Notion. Three years from now, most pre-AI companies will be gone. Notion will be one of the few standing stronger than before. This episode is a field study in how they're pulling it off. Knuckle Up ↓ 00:00 Intro 01:27 What were Notion's core founding principles? 06:20 Which early cultural principles scaled, and which broke? 08:22 How did Notion hire its first employees, and where did they come from? 11:48 How does hiring work now that the founders can't meet everyone? 14:35 Why does Akshay, as COO, prefer to have zero direct reports? 19:05 How do Ivan, Simon, and Akshay divide the work? 21:07 Does Notion's intentionality ever conflict with speed? 25:25 What should other founders steal from Notion's culture? 28:11 When did AI become a reason to rethink the whole product? 30:44 Why were the early AI years a "swamp of despair"? 36:05 How do you push AI across a huge product without losing the user? 39:25 Does Notion buy its AI DNA or build it? 40:44 Should Notion be afraid of OpenAI, Anthropic, and fast copycats? 46:58 What's hardest about the reinvention, and what does "meet the LLM" mean? 52:42 Is Notion AI-native in every function yet? 54:36 Are Notion's engineers still writing code, and how has engineering changed? 1:01:07 Once building is cheap, what's the new bottleneck? 1:02:39 How is AI reshaping sales, marketing, and support? 1:09:07 How many agents run inside Notion, and who builds them? 1:11:28 How has recruiting changed for the AI era? 1:13:48 What still worries Akshay about Notion's future? 1:15:22 Quickfire: admired founders, books, overrated AI advice, and Akshay’s superpower 1:19:42 What should a $50M pre-AI company do in the next 90 days?

Nakul Mandan

205,031 次观看 • 2 个月前