Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

new in langgraph: interrupts with typed response schemas! when your agent pauses for a human, you define what a valid response looks like: 1. responses are validated before they're passed back to the agent 2. you can render a real response form in your UI, not just a json... show more

Sydney Runkle

14,595 subscribers

18,008 views • 7 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

5 Comments

Kizuno187 days ago

typed boundary validation is the single biggest reliability boost for agents: passing unstructured input back to a paused execution graph causes instant state drift. in our autonomous pipeline, pydantic schemas gate all resumption payloads. typed assertions > open-ended json

kai Nakamura7 days ago

Interrupt boundaries need typed contracts.

Hershal Rao7 days ago

my agents can finally fail validation with style

AI Geeker7 days ago

A raw JSON Schema dict is exposed to clients but doesn't validate resume values, per the docs. Use a Pydantic model, TypedDict or dataclass for runtime validation. Test missing fields and type coercion separately.

Gaurav Tewatia7 days ago

Did u used remotion or hyperframe to build this video?

Related Videos

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 views • 3 months ago

Here is how simple it is to build a UI front-end for an AI agent (assuming you are using . The video here is 90 seconds and will show you everything you need to connect an agent to a web app: 1. Set up CopilotKit🪁 in your app 1. Copy the agent's localhost URL from LangGraph Studio 2. Paste that URL into a CopilotKit🪁 remote endpoint That's all you need to get a front-end to interact with the agent! The secret sauce here is CoAgents, an open-source library. You can use CoAgents to integrate any agent with your web application. Here is what you get: • Human-in-the-loop to steer and correct the agent • Stream intermediate agent state • Real-time state sharing between the agent and the application • Agentic generative UI to build trust that the agent is on the right path Watch the attached demo so you see it in action.

Here is how simple it is to build a UI front-end for an AI agent (assuming you are using . The video here is 90 seconds and will show you everything you need to connect an agent to a web app: 1. Set up CopilotKit🪁 in your app 1. Copy the agent's localhost URL from LangGraph Studio 2. Paste that URL into a CopilotKit🪁 remote endpoint That's all you need to get a front-end to interact with the agent! The secret sauce here is CoAgents, an open-source library. You can use CoAgents to integrate any agent with your web application. Here is what you get: • Human-in-the-loop to steer and correct the agent • Stream intermediate agent state • Real-time state sharing between the agent and the application • Agentic generative UI to build trust that the agent is on the right path Watch the attached demo so you see it in action.

Santiago

46,142 views • 1 year ago

PSA: You can connect a Managed Deep Agent to Slack. Mentions, DMs, and thread replies all start a run. Your agent posts its response back in the same conversation. Here’s how to get started ⤵️

PSA: You can connect a Managed Deep Agent to Slack. Mentions, DMs, and thread replies all start a run. Your agent posts its response back in the same conversation. Here’s how to get started ⤵️

LangChain

21,920 views • 23 days ago

Our latest LangChain Academy course – Building Ambient Agents with LangGraph – is now available! Most agents today handle one request at a time through chat interfaces. But as models have improved, agents can now run in the background – and take on long-running, complex tasks. LangGraph is built for these “ambient agents,” with support for human-in-the-loop workflows and memory. LangGraph Platform provides the infrastructure to run these agents at scale, and LangSmith helps you observe, evaluate, and improve your agents. Together, they make it easier to build reliable, production-ready agents. In this course, you’ll: 📩 Learn the fundamentals of LangGraph and how to build your own email agent 📊 Evaluate your agent using LangSmith ✅ Add human-in-the-loop for reviews, and memory so your agent adapts over time 🚀 Deploy your agent with LangGraph Platform and connect it to Gmail

Our latest LangChain Academy course – Building Ambient Agents with LangGraph – is now available! Most agents today handle one request at a time through chat interfaces. But as models have improved, agents can now run in the background – and take on long-running, complex tasks. LangGraph is built for these “ambient agents,” with support for human-in-the-loop workflows and memory. LangGraph Platform provides the infrastructure to run these agents at scale, and LangSmith helps you observe, evaluate, and improve your agents. Together, they make it easier to build reliable, production-ready agents. In this course, you’ll: 📩 Learn the fundamentals of LangGraph and how to build your own email agent 📊 Evaluate your agent using LangSmith ✅ Add human-in-the-loop for reviews, and memory so your agent adapts over time 🚀 Deploy your agent with LangGraph Platform and connect it to Gmail

LangChain

33,192 views • 1 year ago

🚀Launching CoAgents Public Beta 🪁: Everything you need to build Agent-Native applications, powered by LangGraph & CopilotKit. CoAgents enables in-app agents with: - Agenetic generative UI ✨ - Shared state (between agent application) - Streaming intermediate agent state - Human-in-the-Loop (Human approval & planning) 👨‍🦰 - Frontend Actions 💪 --- We’ve recently seen the emergence of Agent-Native applications that actually work: powered by vertical AI agents + agentic UX + deep in-app integration. (Apps like the Replit AI Agent, OpenAI Canvas, etc, but for any domain) With CoAgents + LangGraph, you can build this next generation of agent apps, for any vertical, with a clean and easy to use infrastructure (in hours). 💻Get started: 🗞️Blog: 🕹️Demo: 🗓️Webinar (Build an Agent-Native Apps with CoAgents & LangGraph): CC: Atai Barkai, , Harrison Chase

🚀Launching CoAgents Public Beta 🪁: Everything you need to build Agent-Native applications, powered by LangGraph & CopilotKit. CoAgents enables in-app agents with: - Agenetic generative UI ✨ - Shared state (between agent application) - Streaming intermediate agent state - Human-in-the-Loop (Human approval & planning) 👨‍🦰 - Frontend Actions 💪 --- We’ve recently seen the emergence of Agent-Native applications that actually work: powered by vertical AI agents + agentic UX + deep in-app integration. (Apps like the Replit AI Agent, OpenAI Canvas, etc, but for any domain) With CoAgents + LangGraph, you can build this next generation of agent apps, for any vertical, with a clean and easy to use infrastructure (in hours). 💻Get started: 🗞️Blog: 🕹️Demo: 🗓️Webinar (Build an Agent-Native Apps with CoAgents & LangGraph): CC: Atai Barkai, , Harrison Chase

CopilotKit🪁

51,684 views • 1 year ago

AGENT ID FOR CLAUDE AGENT issue an agent ID to your claude code agent in 2 min - so it can commit to github as a verified, human-authorized agent not just a random bot this is the first step towards building trust in the agentic internet, powered by Alien

AGENT ID FOR CLAUDE AGENT issue an agent ID to your claude code agent in 2 min - so it can commit to github as a verified, human-authorized agent not just a random bot this is the first step towards building trust in the agentic internet, powered by Alien

kirill avery

16,715 views • 6 months ago

Big release here! AG-UI 🤝 Google A2A Embed A2A multi-agent meshes in your frontend, and build fullstack multi-agent apps with A2A and AG-UI. 🔍How it works: Simply drop-in A2A agent endpoints, and an A2A AG-UI orchestrator agent will bi-directionally stream events between your Agents & application. Includes: - UI for A2A Interactions - Generative UI for Agent Tool Calls - Human-in-the Loop Approvals - State Synchronization (agent mesh application state) - Frontend Tool Calls for A2A Agents Watch the demo below > LangGraph & Google ADK agents working together simultaneously inside an app Demo GitHub, docs, and more 👇

Big release here! AG-UI 🤝 Google A2A Embed A2A multi-agent meshes in your frontend, and build fullstack multi-agent apps with A2A and AG-UI. 🔍How it works: Simply drop-in A2A agent endpoints, and an A2A AG-UI orchestrator agent will bi-directionally stream events between your Agents & application. Includes: - UI for A2A Interactions - Generative UI for Agent Tool Calls - Human-in-the Loop Approvals - State Synchronization (agent mesh application state) - Frontend Tool Calls for A2A Agents Watch the demo below > LangGraph & Google ADK agents working together simultaneously inside an app Demo GitHub, docs, and more 👇

CopilotKit🪁

31,845 views • 1 year ago

Demo 2: human + agent design loop inside Codex. Not every workflow needs the agent to drive everything. You design in Open Design. Codex reviews the output. It can inspect files, open pages, test interactions, critique the design, and turn feedback into the next prompt. Design becomes a human + agent feedback loop.

Demo 2: human + agent design loop inside Codex. Not every workflow needs the agent to drive everything. You design in Open Design. Codex reviews the output. It can inspect files, open pages, test interactions, critique the design, and turn feedback into the next prompt. Design becomes a human + agent feedback loop.

Open Design

20,103 views • 4 months ago

“If you’re Prime Minister in three weeks time, what do you fear the most?” Quite a genuinely human response from Keir Starmer. One of the first answers that feels like it is not a ‘campaign mode’ response. #BattleForNo10

“If you’re Prime Minister in three weeks time, what do you fear the most?” Quite a genuinely human response from Keir Starmer. One of the first answers that feels like it is not a ‘campaign mode’ response. #BattleForNo10

Eddie Burfi

957,831 views • 2 years ago

A conversational agent with no hallucinations! This is huge! Here is the $1M problem: Build a customer-facing AI agent that works consistently, doesn't hallucinate, and is fully aligned with the business rules. Check out Parlant, a FREE, open-source library. I've talked about them before, and here is the TL;DR: 1. Parlant gives you 10x more control over what your agent says 2. It helps you control how agents conduct conversations 3. It helps you control the service protocols and rules agents follow 4. It helps you control what agents can and can't say They do something pretty clever: 1. They have a set of predefined potential responses that the agent can use to reply to the customer. 2. When a customer sends a message, the agent generates a fluid response draft using an LLM and matches and renders the closest pre-approved reply template. 3. The agent returns the rendered pre-approved reply, not the one generated by the LLM. This maintains fluidity while avoiding unpredictability. Parlant also uses your domain terminology, invokes your tools, and implements self-critique to craft/evaluate its response iteratively. This pretty much solves any hallucination issues with your agent.

A conversational agent with no hallucinations! This is huge! Here is the $1M problem: Build a customer-facing AI agent that works consistently, doesn't hallucinate, and is fully aligned with the business rules. Check out Parlant, a FREE, open-source library. I've talked about them before, and here is the TL;DR: 1. Parlant gives you 10x more control over what your agent says 2. It helps you control how agents conduct conversations 3. It helps you control the service protocols and rules agents follow 4. It helps you control what agents can and can't say They do something pretty clever: 1. They have a set of predefined potential responses that the agent can use to reply to the customer. 2. When a customer sends a message, the agent generates a fluid response draft using an LLM and matches and renders the closest pre-approved reply template. 3. The agent returns the rendered pre-approved reply, not the one generated by the LLM. This maintains fluidity while avoiding unpredictability. Parlant also uses your domain terminology, invokes your tools, and implements self-critique to craft/evaluate its response iteratively. This pretty much solves any hallucination issues with your agent.

Santiago

64,237 views • 1 year ago

Anthropic's in trouble, again! They spent years building what's now fully open-source. What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box. For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response. Every major AI product tried to replicate it. But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK. So teams started building an owned version that required engineering the entire interface layer from scratch. Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it. To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run. CopilotKit🪁 is now the only open-source framework that actually lets you build your own full-stack Claude-like apps. It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication). Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice. In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like: - generative UI, so the agent renders real components instead of text - chat windows, sidebars, and popups, or a fully headless setup - shared state, so the agent and app stay in sync - human-in-the-loop approvals, where the agent waits before acting - persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time. The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team. CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more. CopilotKit GitHub repo → (don't forget to star it ⭐ ) If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation. Read it below.

Anthropic's in trouble, again! They spent years building what's now fully open-source. What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box. For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response. Every major AI product tried to replicate it. But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK. So teams started building an owned version that required engineering the entire interface layer from scratch. Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it. To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run. CopilotKit🪁 is now the only open-source framework that actually lets you build your own full-stack Claude-like apps. It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication). Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice. In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like: - generative UI, so the agent renders real components instead of text - chat windows, sidebars, and popups, or a fully headless setup - shared state, so the agent and app stay in sync - human-in-the-loop approvals, where the agent waits before acting - persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time. The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team. CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more. CopilotKit GitHub repo → (don't forget to star it ⭐ ) If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation. Read it below.

Avi Chawla

461,550 views • 4 months ago

I present to you my latest fully vibeslopped "I didn't read the code" oeuvre: Jot A self-hosted collaborative markdown editor for you, your friends, and your agents. Like Google Docs, but worse. Try it with me here: Share a note, pick access (view/comment/edit), hand the link to a human or paste the CLI instructions into your agent. They can read, edit, and comment together in real-time.

I present to you my latest fully vibeslopped "I didn't read the code" oeuvre: Jot A self-hosted collaborative markdown editor for you, your friends, and your agents. Like Google Docs, but worse. Try it with me here: Share a note, pick access (view/comment/edit), hand the link to a human or paste the CLI instructions into your agent. They can read, edit, and comment together in real-time.

Mario Zechner

29,316 views • 6 months ago

Today, we're launching a new Laracasts series that will show you the essentials building an AI agent from scratch. We start with a basic chat response and gradually introduce new concepts, such as the agent loop, custom tools, and more. 😀 "So You Want To Build An Agent"

Today, we're launching a new Laracasts series that will show you the essentials building an AI agent from scratch. We start with a basic chat response and gradually introduce new concepts, such as the agent loop, custom tools, and more. 😀 "So You Want To Build An Agent"

Laracasts

16,427 views • 5 months ago

Most AI agents stop at chat. Agent Max is built for what comes after. Max tools. Max control and configurability. Max production readiness. Your agent can use: • any tools, APIs, MCP, and workflows • built-in knowledge: docs/website • multi-model: OpenAI, Claude, Gemini... • agent-to-agent handoffs • human-in-the-loop • logs, usage tracking, environments, and RBAC • enterprise controls for SOC2/GDPR/HIPAA/ISO needs • hosted chat UI, API, Skill in agents, Slack, WhatsApp, Teams, Voice, and more Agent Max is live now in BuildShip for everyone. Give it a try, or comment/DM to book a demo if you want help setting up your first agent.

Most AI agents stop at chat. Agent Max is built for what comes after. Max tools. Max control and configurability. Max production readiness. Your agent can use: • any tools, APIs, MCP, and workflows • built-in knowledge: docs/website • multi-model: OpenAI, Claude, Gemini... • agent-to-agent handoffs • human-in-the-loop • logs, usage tracking, environments, and RBAC • enterprise controls for SOC2/GDPR/HIPAA/ISO needs • hosted chat UI, API, Skill in agents, Slack, WhatsApp, Teams, Voice, and more Agent Max is live now in BuildShip for everyone. Give it a try, or comment/DM to book a demo if you want help setting up your first agent.

BuildShip

75,982 views • 3 months ago

2 Cursor agents in separate tabs chat and plan the most interesting app ever and build it too! collaboratively All you need is 2 rules, THAT IS IT! here is how: create 2 rule files set to "Manual" agent-1 .mdc: --- You are agent-1 you will be chatting with agent-2 to design and build the most interesting python app ever you will write to agent_1.txt file and read from agent_2.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built you start the conversation --- agent-2 .mdc: --- You are agent-2 you will be chatting with agent-1 to design and build the most interesting python app ever you will write to agent_2.txt file and read from agent_1.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built agent-1 will start the convo --- create a new agent tab, you should have 2 tabs assign agent 1 its rule and agent 2 its rule type "begin" for agent 1 and enter type "begin" for agent 2 and enter That is it! and then watch them go to work! --- Want to level up your Cursor game? I’ve created a 45-chapter course on mastering Cursor. Check it out via the link in my bio! each chapter is short and independent and designed to get your started quickly featuring 26 hours of content where we build interesting apps and ideas from scratch in each chapter. ---

2 Cursor agents in separate tabs chat and plan the most interesting app ever and build it too! collaboratively All you need is 2 rules, THAT IS IT! here is how: create 2 rule files set to "Manual" agent-1 .mdc: --- You are agent-1 you will be chatting with agent-2 to design and build the most interesting python app ever you will write to agent_1.txt file and read from agent_2.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built you start the conversation --- agent-2 .mdc: --- You are agent-2 you will be chatting with agent-1 to design and build the most interesting python app ever you will write to agent_2.txt file and read from agent_1.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built agent-1 will start the convo --- create a new agent tab, you should have 2 tabs assign agent 1 its rule and agent 2 its rule type "begin" for agent 1 and enter type "begin" for agent 2 and enter That is it! and then watch them go to work! --- Want to level up your Cursor game? I’ve created a 45-chapter course on mastering Cursor. Check it out via the link in my bio! each chapter is short and independent and designed to get your started quickly featuring 26 hours of content where we build interesting apps and ideas from scratch in each chapter. ---

echo.hive

88,611 views • 1 year ago

Antigravity 2.0 now features a dedicated planning mode, just like the Antigravity CLI. Type /plan and the agent steps back to think through the task, and conduct extensive research, before generating an implementation plan for your review. The agent will ask for your approval before it begins executing on the task. You can also ask for a plan naturally in your prompt, for a lighter version of a plan.

Antigravity 2.0 now features a dedicated planning mode, just like the Antigravity CLI. Type /plan and the agent steps back to think through the task, and conduct extensive research, before generating an implementation plan for your review. The agent will ask for your approval before it begins executing on the task. You can also ask for a plan naturally in your prompt, for a lighter version of a plan.

Google Antigravity

2,380,467 views • 12 days ago

i spun up a paid API endpoint in under a minute on Bankr x402 Cloud. its a demo AI agent that finds DoorDash restaurant recs for your area. public URL, searchable in the marketplace, inference powered by the Bankr LLM Gateway. we shipped interactive mode for the Bankr CLI. any x402 endpoint you deploy can define typed JSON schema for inputs and outputs. the CLI reads the schema, prompts you for each field, and shows you exactly what you're paying before you submit. agents and humans can discover and call your service without reading docs. just "bankr x402 call -i " and go. check out the demo. links in the next post.

i spun up a paid API endpoint in under a minute on Bankr x402 Cloud. its a demo AI agent that finds DoorDash restaurant recs for your area. public URL, searchable in the marketplace, inference powered by the Bankr LLM Gateway. we shipped interactive mode for the Bankr CLI. any x402 endpoint you deploy can define typed JSON schema for inputs and outputs. the CLI reads the schema, prompts you for each field, and shows you exactly what you're paying before you submit. agents and humans can discover and call your service without reading docs. just "bankr x402 call -i " and go. check out the demo. links in the next post.

deployer

13,300 views • 6 months ago

Hermes agent supports Browserbase to browse and interact the web just like a human. You can add it when you setup your agent, or add it with Watch it add deodorant to my amazon cart, something much needed for engineers around the world.

Hermes agent supports Browserbase to browse and interact the web just like a human. You can add it when you setup your agent, or add it with Watch it add deodorant to my amazon cart, something much needed for engineers around the world.

Kyle Jeong

28,034 views • 6 months ago

You can also now create automations without any attached repos, like a daily Slack digest agent that prioritizes unread threads and DMs for your response. Find more templates in our marketplace:

You can also now create automations without any attached repos, like a daily Slack digest agent that prioritizes unread threads and DMs for your response. Find more templates in our marketplace:

Cursor

33,951 views • 4 months ago