Skip to main content
Remote execution enables you to run agents, teams, and workflows that are hosted on remote AgentOS instances. This is useful for:
  • Distributed architectures: Run specialized agents on different servers
  • Microservices: Decompose your agentic system into independent services
  • Gateway pattern: Create a unified API for multiple AgentOS instances
Agno supports remote connections to AgentOS instances and A2A-compatible servers.See RemoteAgent, RemoteTeam, and RemoteWorkflow for more information.

Core Components

RemoteAgent

Execute agents on remote AgentOS instances

RemoteTeam

Execute teams on remote AgentOS instances

RemoteWorkflow

Execute workflows on remote AgentOS instances

AgentOSClient

Low-level client for direct API access to any AgentOS endpoint

A2AClient

Low-level client for direct API access to any A2A endpoint

Quick Start

1. Set Up a Remote AgentOS Server

First, create and run an AgentOS instance that will host your agents:
Run the server:

2. Connect and Execute Remotely

Use RemoteAgent to execute the agent from another application:

3. Create an AgentOS Gateway

Create a gateway that aggregates multiple AgentOS instances:
See Gateway Pattern for more details.

Connecting to A2A-compatible servers

Using the A2A protocol, you can connect to any A2A-compatible server. Here is an example of connecting to a Google ADK A2A server:

Learn More

Remote Agent

Detailed guide on using RemoteAgent

Remote Team

Detailed guide on using RemoteTeam

Remote Workflow

Detailed guide on using RemoteWorkflow

Gateway Pattern

Create a unified API gateway for multiple AgentOS instances