正在加载视频...

视频加载失败

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

64,237 次观看 • 1 年前 •via X (Twitter)

11 条评论

Santiago 的头像
Santiago1 年前

Here is the GitHub repository: And here is a paper showing the prompt engineering method Parlant uses behind the scenes (4.8% more accurate than Chain of Thought!):

AskLex.ai 的头像
AskLex.ai1 年前

Have AI answers to legal questions reviewed by a real lawyer instantly.

Mind Prison 的头像
Mind Prison1 年前

Sounds like the pre-LLM bots. Predefined responses. So we have gone full circle? Billions of dollars for slightly better predefined chatbot responses?

Santiago 的头像
Santiago1 年前

"Slightly better predefined responses" is a solution that's indeed worth billions of dollars

Karl 的头像
Karl1 年前

TBH that idea is quite old (m$ bot framework and intents etc). LLMs are only more general. Not allowing hallucinations is not resolving them. It's like not leaving your street to avoid a robbery.

luizfcouto 的头像
luizfcouto1 年前

Love this! Pre approved templates are a smart way to avoid hallucinations with full control. We’ve been using Guardrail AI Agents, a bit more dynamic, with layered rules and validations instead of fixed replies. But honestly, combining both feels like the sweet spot for flexibility and safety.

Tech Brief Ai 的头像
Tech Brief Ai1 年前

This is a game-changer. Parlant’s hybrid approach — LLM creativity + strict response control — is exactly what customer-facing AI needs. You get natural, on-brand conversations without the risk of rogue replies or hallucinations. It’s not just smart — it’s deployment-ready. If you’re building serious AI agents for business, this isn’t optional anymore. It’s the new standard.

Danon 🛡️ 的头像
Danon 🛡️1 年前

How to use genAI to mimic the legacy NLU based chatbots 🤣. Probabilistic behavior is not a bug, but a feature. You don't hire a human agent for your contact center and tell him you are only allowed to use this list of pre approved sentences...

zee | ai web scraper 的头像
zee | ai web scraper1 年前

So...use llm to choose which reply from the ancient chat bot to reply with? Lol hard pass

Arpit Sharma 的头像
Arpit Sharma1 年前

Most agents today either sound robotic or go off-script entirely. This approach feels like it could finally bridge that gap.

Lukas Bug 的头像
Lukas Bug1 年前

“No hallucinations” and “LLM” are mutually exclusive

相关视频

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 次观看 • 9 天前

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

Andrew Ng

105,343 次观看 • 1 年前

New short course: Serverless Agentic Workflows with Amazon Bedrock. Learn to build and deploy serverless agents in this course created with Amazon Web Services and taught by Mike G Chambers, a Senior Developer Advocate at AWS specializing in GenAI. (Disclosure: I serve on Amazon's board.) Generative AI applications are becoming more complex, sophisticated, and agentic. Agentic applications have workloads that can be hard to predict in advance -- for example, what tools will it decide to call? -- and a serverless architecture helps you efficiently providing on-demand resources. This course teaches you to build and deploy a serverless agentic application. You’ll learn to create agents with tools, code execution, and guardrails, and build responsible agents for business use cases: - Build a customer service bot for a fictional tea mug business that can answering questions, retrieve information, and process orders. - Connect your customer service agent to a CRM to get customer info and log support tickets in real-time. - Explore how you invoke the agent, and see the trace to review the agent’s thought process and observation loop until it reaches its final output. - Attach a code interpreter to your agent, giving it the ability to perform accurate calculations by writing and running its own Python code. - Implement guardrails to prevent your agent from revealing sensitive information or using inappropriate language. By the end, you will have built a sophisticated AI agent capable of handling real-world customer support scenarios. Please sign up here!

Andrew Ng

81,048 次观看 • 1 年前

🚀Exciting News: The Lit Agent Wallet is Now an elizaOS Plugin! 🚀 We’re thrilled to share that the Lit Agent Wallet—a decentralized system that empowers agents with a private key stored securely across an MPC + TEE network (Lit)—is now available as a plugin for ElizaOS!🎉 This integration brings unparalleled flexibility and security to your decentralized workflows. Whether you're an EOA, a smart account, or a DAO, you can now set tools and policies on-chain that your agents can use, all while ensuring your private keys remain secure and decentralized. 🔒 What Does This Mean for You? >Enhanced Security: Private keys are fragmented and stored across the Lit network, leveraging MPC (Multi-Party Computation) and TEE (Trusted Execution Environment) for maximum security. >On-Chain Control: Set and manage tools, policies, and permissions directly on-chain, giving users and DAOs full control over what your agents can do. >Seamless Integration: As an ElizaOS plugin, the Lit Agent Wallet is now easier than ever to integrate into your existing workflows. Check out the video for a walk through of the setup, configuration, and use cases of the Lit Agent Wallet within ElizaOS. We’ll show you just how easy it is to get started and unlock the full potential of decentralized agents. Get Started Today! Ready to take your agent operations to the next level? Install the Lit Agent Wallet plugin on ElizaOS and experience the future of secure, on-chain agent asset management. 🔗 🔗 Let’s build a more intelligent and decentralized future together! 🌐

Lit Protocol 🔑

41,989 次观看 • 1 年前