AgentProtocol and behaves like a native Agent for routing, streaming and session persistence.
Supported Frameworks
| Framework | Adapter | Install |
|---|---|---|
| Claude Agent SDK | ClaudeAgent | uv pip install claude-agent-sdk |
| LangGraph | LangGraphAgent | uv pip install langgraph langchain-openai |
| DSPy | DSPyAgent | uv pip install dspy |
.run() and .print_response().
See the per-framework pages for more examples.
What Works and What Doesn’t
The adapters cover the basics every AgentOS deployment needs (registration, streaming, sessions, tool visibility).
Agno-specific capabilities like delegation, knowledge, dependencies, and hooks live on the native
Agent and Team and are not available through external frameworks.| Capability | Supported | Notes |
|---|---|---|
AgentOS(agents=[...]) registration | ✅ | Adapters satisfy AgentProtocol |
/agents and /agents/{id}/runs endpoints | ✅ | Same routes as native agents |
| SSE streaming | ✅ | Token and tool call events emitted by adapters |
| Session persistence | ✅ | When db is set on AgentOS |
Standalone .run() / .print_response() | ✅ | Sync and async |
| Tool call visibility in the UI | ✅ | Wrapped as Agno tool events |
Use as a Team member | - | Agno Team orchestration is built around the native Agent |
| Memory, knowledge, dependencies, hooks, guardrails | - | These are Agno-SDK concepts wired into the native Agent |
| Structured input and output | - | Use the framework’s own typing (DSPy signatures, LangGraph state) |
| Skills, reasoning, learning | - | Native Agent only |
Next Steps
Claude Agent SDK
Run Claude Code as an AgentOS agent.
LangGraph
Wrap a compiled LangGraph graph.
DSPy
Serve a DSPy program (Predict, ChainOfThought, ReAct).