Reuse Existing Agents
Add agents you've already built to a workforce, keeping their configuration intact.
Overview
You don't always need to create new agents for your workforce. If you already have deployed agents with proven configurations, you can add them directly to any workforce. The agent keeps its own prompt, tools, and knowledge base - only reporting lines and shared memory access are added.
- System prompt
- Tool integrations
- Knowledge base
- Approval policies
- Voice settings
- Reporting lines (delegation paths)
- Shared memory access
- Workforce membership
- Telegram workspace (if configured)
How to Add Existing Agents
Open the Member Library
In the Workforce Builder, click the Member Library button in the toolbar or use the "Add Custom Agent" option at the bottom of the left sidebar.
Browse Your Agents
The library shows all your deployed agents. You'll see:
- Agent name and role
- Deployment status
- Tools currently configured
- Which workforces they're already in (if any)
Drag onto Canvas
Click and drag the agent from the library onto your workforce canvas. The agent appears as a new node that you can position and connect.
Connect Reporting Lines
Create reporting lines by dragging from the existing workforce members to your new agent (or vice versa, depending on hierarchy).
Save & Deploy
Save your workforce. The agent is now part of the team with access to shared memory and configured delegation paths.
Agent in Multiple Workforces
A single agent can belong to multiple workforces simultaneously. This is useful when:
Shared Specialists
A research agent used by both your Sales Team and Marketing Team workforces.
Cross-functional Support
A knowledge base agent that serves multiple department workforces.
Editing Reused Agents
Clicking the agent in the workforce canvas lets you:
- Adjust reporting lines
- View (but not edit) core configuration
- Remove from this workforce
To edit the agent's core configuration:
- Go to your main agent dashboard
- Edit the agent directly
- Changes apply everywhere it's used
Best Practices
Do
- Reuse well-tested agents with proven configurations
- Use specialists across multiple teams when logical
- Keep agent names descriptive for easy identification
- Document which workforces use shared agents
Avoid
- Reusing agents that need different configs per workforce
- Adding the same agent to too many workforces (gets confusing)
- Editing shared agents without checking impact
- Creating circular dependencies across workforces