Loading video...

Video Failed to Load

Go Home

Training AI agents with reinforcement learning can be challenging because their tools, context, and decision-making are managed by complex frameworks. Agent Lightning connects existing agents to RL training, making it easier to improve them without rebuilding them.:

18,815 views • 18 days ago •via X (Twitter)

4 Comments

Yousaf AI's profile picture
Yousaf AI17 days ago

The possibilities are endless.

Peter Orban's profile picture
Peter Orban18 days ago

Plugging existing agents into RL training without rebuilding them is huge. Lowering that barrier could make agent improvement way more accessible for builders 🔥

EKOS _ OMiD🇮🇷's profile picture
EKOS _ OMiD🇮🇷18 days ago

RL gives agents a way to learn from execution. I think there’s another question worth asking: what happens to the useful knowledge inside those executions after the model gets updated? Not every lesson should disappear into a weight update. Some should remain traceable and reusable by the next agent. That distinction is pretty important.

Zain akram's profile picture
Zain akram18 days ago

The more interesting implication here is that RL for agents flips the bottleneck — the environment becomes the constraint, not model capacity. Flaky tools and slow APIs probably shape the reward signal more than the policy itself.

Related Videos

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,839 views • 1 year ago