Skip to content

AG-UI (Agent User Interface) agents connect to remote HTTP endpoints that implement the AG-UI protocol, enabling integration of any AG-UI compatible server into the LLMling-Agent pool.

Overview

AG-UI is a protocol for building agent interfaces that provides:

  • HTTP-based communication: Simple REST endpoints for agent interaction
  • Streaming support: Real-time response streaming
  • Standardized interface: Consistent API across different agent implementations

AG-UI agents are useful for:

  • Integrating existing AG-UI compatible services
  • Building distributed agent architectures
  • Connecting to remote agent deployments
  • Testing with locally spawned servers

Configuration Reference

AG-UI Agent Configuration

Configuration for AG-UI protocol agents.

AG-UI agents connect to remote HTTP endpoints that implement the AG-UI protocol, enabling integration of any AG-UI compatible server into the llmling-agent pool.

Example:

agui_agents:
  remote_assistant:
    endpoint: http://localhost:8000/agent/run
    timeout: 30.0
    headers:
      X-API-Key: ${API_KEY}
    tools:
      - import_path: mymodule.my_tool_function

  managed_agent:
    endpoint: http://localhost:8765/agent/run
    startup_command: "uv run ag-ui-server config.yml"
    startup_delay: 3.0
    tools:
      - import_path: package.tool_one
      - import_path: package.tool_two

AG-UI Agent Configuration (YAML)
- endpoint: http://localhost:8000/agent/run
  timeout: 60.0  # Request timeout in seconds.
  headers: {}  # Additional HTTP headers to send with requests.
  startup_command: null  # Optional shell command to start the AG-UI server automatically.
  startup_delay: 2.0  # Seconds to wait after starting server before connecting.
  tools: []  # Tools to expose to the remote agent for client-side execution.
  name: null  # Identifier for the node. Set from dict key, not from YAML.
  config_file_path: null  # Config file path for resolving relative paths.
  display_name: null  # Human-readable display name for the node.
  description: null  # Optional description of the agent / team.
  triggers: []  # Event sources that activate this agent / team
  connections: []  # Targets to forward results to.
  mcp_servers: []  # List of MCP server configurations:
  input_provider: null  # Provider for human-input-handling.
  event_handlers: []  # Event handlers for processing agent stream events.

Basic Usage

agui_agents:
  remote_assistant:
    endpoint: http://localhost:8000/agent/run
    timeout: 30.0
    headers:
      X-API-Key: ${API_KEY}

  managed_agent:
    endpoint: http://localhost:8765/agent/run
    startup_command: "uv run ag-ui-server config.yml"
    startup_delay: 3.0

Configuration Notes

  • The endpoint field specifies the HTTP URL for the AG-UI agent server
  • Use headers for authentication tokens or custom routing headers
  • Environment variables can be used in header values: ${VAR_NAME}
  • When startup_command is provided, LLMling-Agent will spawn the server process
  • The server process is automatically terminated when the agent pool closes
  • Use startup_delay to give the server time to initialize before connecting
  • The timeout setting controls the maximum time for agent responses