Sub Agents Configuration

Overview

A Digital Employee can be composed of a coordinator agent plus one or more sub-agents. Sub-agents are attached as nested agents on the underlying glaip_sdk.Agent instance.

In this repository, see examples/configuration_propagation_example.py for a working example (including config propagation).

Key Concepts

What is a “sub-agent”?

A sub-agent is a glaip_sdk.Agent instance attached under the coordinator agent. At deploy-time, DigitalEmployee builds a single root Agent and passes sub-agents into the Agent(..., agents=[...]) field.

How sub-agents are attached

You attach sub-agents by providing them to DigitalEmployee:

• DigitalEmployee(sub_agents=[...]) (recommended)

• digital_employee.add_sub_agents([...])

Configuration propagation (tools + MCPs)

When the Digital Employee is deployed, it will process sub_agents and automatically propagate tool/MCP configs from the parent to sub-agents when:

• The sub-agent uses a tool/MCP.

• The sub-agent does not already define a config for that tool/MCP.

Notes:

• Existing sub-agent configs take precedence over propagated configs.

• Propagation is recursive: nested sub-agents (sub-agents of sub-agents) are processed as well.

• Currently only glaip_sdk.Agent is supported as a sub-agent type; unsupported types are skipped with a warning.

Minimal Example

1) Create a coordinator Digital Employee

from digital_employee_core import DigitalEmployeeIdentity, DigitalEmployeeJob

job = DigitalEmployeeJob(
    title="Coordinator",
    description="Delegates tasks to specialists",
    instruction="You are the coordinator. Delegate tasks to your sub-agents.",
)
identity = DigitalEmployeeIdentity(name="Coordinator", email="[e-mail]", job=job)

2) Define one or more sub-agents

from glaip_sdk import Agent

reminder_agent = Agent(
    name="ReminderAgent",
    instruction="You are a reminder specialist.",
)

3) Attach sub-agents and deploy

from digital_employee_core import DigitalEmployee

digital_employee = DigitalEmployee(
    identity=identity,
    sub_agents=[reminder_agent],
)

digital_employee.deploy()

Notes / Best Practices

• Add or remove sub-agents before deploy; changes after deploy require re-deploying to update the agent graph.

• Prefer stable, unique Agent.name values (removal uses name matching).

• If sub-agents use MCPs/tools that require configs, prefer putting shared configs on the parent DigitalEmployee.configurations and rely on propagation; override only when a sub-agent needs different settings.