Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Software engineers are going to love this! I found an open-source error monitoring agent that scans production logs, finds the root cause, and sends a Slack message with full context before you even notice something broke. Cuts down production downtime by 95%! Check this:

akshay_pachaar's profile picture

Akshay 🚀

284,426 subscribers

181,414 Aufrufe • vor 6 Monaten •via X (Twitter)

BildungGesundheit & WellnessWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I started a company! Introducing Melty, an open source AI code editor for 10x engineers. It's the first editor that understands what you’re doing from the terminal to GitHub and collaborates with you to write production-ready code.
0:46

I started a company! Introducing Melty, an open source AI code editor for 10x engineers. It's the first editor that understands what you’re doing from the terminal to GitHub and collaborates with you to write production-ready code.

Charlie Holtz

582,738 Aufrufe • vor 2 Jahren

🚀 New LangChain Academy Course: Building Reliable Agents 🚀 Shipping agents to production is hard. Traditional software is deterministic – when something breaks, you check the logs and fix the code. But agents rely on non-deterministic models. Add multi-step reasoning, tool use, and real user traffic, and building reliable agents becomes far more complex than traditional system design. The goal of this course is to teach you how to take an agent from first run to production-ready system through iterative cycles of improvement. You’ll learn how to do this with LangSmith, our agent engineering platform for observing, evaluating, and deploying agents. Enroll for free ➡️
2:02

🚀 New LangChain Academy Course: Building Reliable Agents 🚀 Shipping agents to production is hard. Traditional software is deterministic – when something breaks, you check the logs and fix the code. But agents rely on non-deterministic models. Add multi-step reasoning, tool use, and real user traffic, and building reliable agents becomes far more complex than traditional system design. The goal of this course is to teach you how to take an agent from first run to production-ready system through iterative cycles of improvement. You’ll learn how to do this with LangSmith, our agent engineering platform for observing, evaluating, and deploying agents. Enroll for free ➡️

LangChain

30,744 Aufrufe • vor 6 Monaten

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic
7:55

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic

Gbenga Akindolani |AI Engineer | Automation Expert

46,436 Aufrufe • vor 3 Monaten

You probably have thousands of agent traces sitting in production. And most of them are doing nothing for you. Today we’re launching the new Kitaru to change that. Kitaru ingests traces from Langfuse, Braintrust, or any OTel source, investigates what went right and wrong, groups recurring failures into cohorts, and builds evaluators around them. Then you can replay those same production cases against a different model, prompt, context, or agent setup and ask: What would have happened if we changed this? Instead of traces being something you inspect after a failure, they become part of a continuous improvement loop. Open source. Free to use. Try it out today:
1:35

You probably have thousands of agent traces sitting in production. And most of them are doing nothing for you. Today we’re launching the new Kitaru to change that. Kitaru ingests traces from Langfuse, Braintrust, or any OTel source, investigates what went right and wrong, groups recurring failures into cohorts, and builds evaluators around them. Then you can replay those same production cases against a different model, prompt, context, or agent setup and ask: What would have happened if we changed this? Instead of traces being something you inspect after a failure, they become part of a continuous improvement loop. Open source. Free to use. Try it out today:

Hamza Tahir

22,264 Aufrufe • vor 1 Monat

Jason Calacanis: Anthropic, OpenAI and others are trying to kill OpenClaw Why? Because an open source agent platform is an existential threat to frontier model companies. @jason: “ People are going to say I'm a conspiracy theorist, but the number one goal, I believe, in the large language model, frontier model space, is to kill (OpenClaw). This is a giant movement to stop it, because this is the equivalent of having an open source Android-like player in the market, and that could be incredibly disruptive. Because, I believe, open source is going to win the day on the large language models and take 90% of the token usage, and I think the entire frontier model space could be undercut by open source. And I think they realize that SLMs, the smaller language models that are verticalized now, that will run on desktops and laptops and are even starting to run on the top ones, that is their biggest competitive threat, and I hope it happens.”
0:41

Jason Calacanis: Anthropic, OpenAI and others are trying to kill OpenClaw Why? Because an open source agent platform is an existential threat to frontier model companies. @jason: “ People are going to say I'm a conspiracy theorist, but the number one goal, I believe, in the large language model, frontier model space, is to kill (OpenClaw). This is a giant movement to stop it, because this is the equivalent of having an open source Android-like player in the market, and that could be incredibly disruptive. Because, I believe, open source is going to win the day on the large language models and take 90% of the token usage, and I think the entire frontier model space could be undercut by open source. And I think they realize that SLMs, the smaller language models that are verticalized now, that will run on desktops and laptops and are even starting to run on the top ones, that is their biggest competitive threat, and I hope it happens.”

The All-In Podcast

64,677 Aufrufe • vor 5 Monaten

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

229,172 Aufrufe • vor 5 Monaten

Most agent demos are stateless. Ask → answer → context gone. Production agents need to run for days — pausing, resuming, persisting state. Addy Osmani joins Smitha Kolan on the Agent Factory to build three real agents with ADK 2.0 and Gemini 3.5 Flash, including one that runs Doom in the browser. Check out this episode and more in the Agent Factory series →
5:58

Most agent demos are stateless. Ask → answer → context gone. Production agents need to run for days — pausing, resuming, persisting state. Addy Osmani joins Smitha Kolan on the Agent Factory to build three real agents with ADK 2.0 and Gemini 3.5 Flash, including one that runs Doom in the browser. Check out this episode and more in the Agent Factory series →

Google for Developers

13,939 Aufrufe • vor 3 Monaten

What does work look like when you have more agent employees than teammates? Buzz is the closest answer I've seen. An open source app built on an open protocol, out of Block. I have no affiliation with any of it. It's close. It's not there yet, but it's close. Which is exactly why it's worth an afternoon: You love it and forget about Slack. You hate it and finally configure Slack the way you should have from the start. Either way you watched agent-native software get built in the open, by the people using it. There is no losing in this situation. The people who live in the future are the ones who can look around the corner. Go get your hands dirty.
3:05

What does work look like when you have more agent employees than teammates? Buzz is the closest answer I've seen. An open source app built on an open protocol, out of Block. I have no affiliation with any of it. It's close. It's not there yet, but it's close. Which is exactly why it's worth an afternoon: You love it and forget about Slack. You hate it and finally configure Slack the way you should have from the start. Either way you watched agent-native software get built in the open, by the people using it. There is no losing in this situation. The people who live in the future are the ones who can look around the corner. Go get your hands dirty.

The Startup Ideas Podcast (SIP) 🧃

16,314 Aufrufe • vor 1 Monat

How do you guide an AI agent to open PRs on your behalf? 👀 You give it skills. With the Make Contribution agent skill, Copilot CLI automatically finds and follows a repo's contribution guidelines and templates before acting. Get this skill.👇
1:54

How do you guide an AI agent to open PRs on your behalf? 👀 You give it skills. With the Make Contribution agent skill, Copilot CLI automatically finds and follows a repo's contribution guidelines and templates before acting. Get this skill.👇

GitHub

76,663 Aufrufe • vor 7 Monaten

Finally, a browser automation framework for Agents that actually works in production (open-source)! Typical browser automation tools like Selenium or Playwright require you to hard-code automation. These are brittle since one change in the website can disrupt the full workflow. On the other hand, high-level Agents like OpenAI Operator can be unpredictable in production. Stagehand is an open-source framework that bridges the gap between: - brittle traditional automation like Playwright, Selenium, etc. and - unpredictable full-agent solutions like OpenAI Operator. Key features: - Use AI when you want to navigate unfamiliar pages. - Use code (Playwright) when you know exactly what to do. - Preview AI actions before running them. - Cache repeatable actions to save tokens. - Compatible with SOTA computer use models with just one line of code. - Available in both Python and TypeScript SDK. Stagehand also has an open-source MCP server. Find a link to the repo in the comments! 👉 Over to you: Would you use this instead of Selenium?
0:24

Finally, a browser automation framework for Agents that actually works in production (open-source)! Typical browser automation tools like Selenium or Playwright require you to hard-code automation. These are brittle since one change in the website can disrupt the full workflow. On the other hand, high-level Agents like OpenAI Operator can be unpredictable in production. Stagehand is an open-source framework that bridges the gap between: - brittle traditional automation like Playwright, Selenium, etc. and - unpredictable full-agent solutions like OpenAI Operator. Key features: - Use AI when you want to navigate unfamiliar pages. - Use code (Playwright) when you know exactly what to do. - Preview AI actions before running them. - Cache repeatable actions to save tokens. - Compatible with SOTA computer use models with just one line of code. - Available in both Python and TypeScript SDK. Stagehand also has an open-source MCP server. Find a link to the repo in the comments! 👉 Over to you: Would you use this instead of Selenium?

Avi Chawla

101,419 Aufrufe • vor 1 Jahr

HERMES AGENT IS THE MOST POWERFUL OPEN SOURCE AI AGENT FRAMEWORK AVAILABLE RIGHT NOW — AND MOST PEOPLE HAVE NO IDEA HOW TO USE IT PROPERLY. This masterclass fixes that completely. From zero to a fully operational autonomous agent system in one sitting. Installation. Skills. Memory. MCP servers. Scheduler. Multi-agent operations. Every section builds on the previous one. The people who read this this weekend will have a production-ready autonomous agent operation running by Monday. Read this and bookmark it now.
1:05

HERMES AGENT IS THE MOST POWERFUL OPEN SOURCE AI AGENT FRAMEWORK AVAILABLE RIGHT NOW — AND MOST PEOPLE HAVE NO IDEA HOW TO USE IT PROPERLY. This masterclass fixes that completely. From zero to a fully operational autonomous agent system in one sitting. Installation. Skills. Memory. MCP servers. Scheduler. Multi-agent operations. Every section builds on the previous one. The people who read this this weekend will have a production-ready autonomous agent operation running by Monday. Read this and bookmark it now.

CyrilXBT

34,633 Aufrufe • vor 3 Monaten

Gigi showed why Drake is the GOAT and is will respected. I love how she shut down the negativity before it even began while promoting the five-part series she is part of, "Magic City," produced by Drake's production company. I can't wait to see this.
2:39

Gigi showed why Drake is the GOAT and is will respected. I love how she shut down the negativity before it even began while promoting the five-part series she is part of, "Magic City," produced by Drake's production company. I can't wait to see this.

industrypolitics

31,369 Aufrufe • vor 1 Jahr

okay Higgsfield Supercomputer is genuinely insane 🤯 it scans your competitors every Monday and drafts 3 ads before you open your laptop it's a cloud-native AI agent built for end-to-end creative production no local setup. runs in your browser or Telegram. here's what it actually does: → orchestrates every major model Claude Opus 4.7, GPT-5.5 Pro, Gemini 3.1 Pro, plus every image and video model → three layers of memory brief it once, it remembers context across every session → 40+ built-in tools with Skills you teach once and trigger with a slash command → scheduled tasks daily ad variations, weekly competitor scans, monthly content calendars → connects to Slack, Drive, Notion, Gmail, Figma and 30+ more powered by enhanced Hermes Agent Higgsfield was an AI video tool, this isn't a video tool anymore it's the whole studio.
1:26

okay Higgsfield Supercomputer is genuinely insane 🤯 it scans your competitors every Monday and drafts 3 ads before you open your laptop it's a cloud-native AI agent built for end-to-end creative production no local setup. runs in your browser or Telegram. here's what it actually does: → orchestrates every major model Claude Opus 4.7, GPT-5.5 Pro, Gemini 3.1 Pro, plus every image and video model → three layers of memory brief it once, it remembers context across every session → 40+ built-in tools with Skills you teach once and trigger with a slash command → scheduled tasks daily ad variations, weekly competitor scans, monthly content calendars → connects to Slack, Drive, Notion, Gmail, Figma and 30+ more powered by enhanced Hermes Agent Higgsfield was an AI video tool, this isn't a video tool anymore it's the whole studio.

Vaibhav Sisinty

17,975 Aufrufe • vor 4 Monaten

A production issue shouldn't require a detective Yet that's how most observability works today Most observability tools just dump alerts. Duplicates, no context, and you still fix it yourself Nicolò Magnante (YC P26) and his cofounder Arseniy Shishaev (YC P26) - who spent years building part of Datadog's metrics product - think that's backwards So they built Superlog (YC P26): Observability that's meant never to be opened A wizard scans your repo, installs proper OpenTelemetry, and runs daily to keep up as you ship When something breaks, it groups the errors into one incident, investigates with full context - logs, traces, recent deploys, past Slack threads - and drops a single mergeable PR in Slack. Merge it Ignore it Or open it in Claude Code and tweak it Vendor-neutral, so you keep every log, trace, and metric - even if you leave Not another notification. A fix. Nicolò Magnante (YC P26) CEO & Co-Founder Superlog (YC P26) on Fondo.com START Huge thanks to Eragon for making this episode possible!
1:12

A production issue shouldn't require a detective Yet that's how most observability works today Most observability tools just dump alerts. Duplicates, no context, and you still fix it yourself Nicolò Magnante (YC P26) and his cofounder Arseniy Shishaev (YC P26) - who spent years building part of Datadog's metrics product - think that's backwards So they built Superlog (YC P26): Observability that's meant never to be opened A wizard scans your repo, installs proper OpenTelemetry, and runs daily to keep up as you ship When something breaks, it groups the errors into one incident, investigates with full context - logs, traces, recent deploys, past Slack threads - and drops a single mergeable PR in Slack. Merge it Ignore it Or open it in Claude Code and tweak it Vendor-neutral, so you keep every log, trace, and metric - even if you leave Not another notification. A fix. Nicolò Magnante (YC P26) CEO & Co-Founder Superlog (YC P26) on Fondo.com START Huge thanks to Eragon for making this episode possible!

David J Phillips

40,983 Aufrufe • vor 3 Monaten

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.
5:56

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

Santiago

26,981 Aufrufe • vor 2 Monaten

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.
0:45

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 Aufrufe • vor 1 Jahr

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.
23:07

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.

Santiago

51,527 Aufrufe • vor 1 Jahr