Skip to main content
The Agent Manager toolkit lets you create and manage agents in a project: generate from a prompt or config, list and inspect agents, update personalities and toolkits, validate configuration, and run mocked end-to-end tests. It does not use OAuth or an API key — access is based on your EKB project membership and Agents permissions. This toolkit is mainly used from Autopilot (Build mode) and similar build surfaces. It is not meant to be nested onto every agent as a normal customer integration (you cannot attach Agent Manager onto an agent you create through Agent Manager itself).

​
Prerequisites

  • Permission to edit agents in the target project (Agents edit for create/update/delete/clone/test)
  • Project membership for read-only operations (list, get, validate, connection checks)
  • When working from the read-only Autopilot system project, always choose a target project for create and mutate operations

​
Available tools

​
Use cases

  • Scaffold a support or research agent from a short description in Autopilot Build mode
  • Clone a proven agent, then adjust personality and toolkits
  • Validate toolkit config before publishing an agent
  • Check which connections are still missing after attaching Gmail, Jira, or similar toolkits

​
Tips

  • Always set the target project for create/update/delete when you are not already inside that project (required from the Autopilot default project).
  • Prefer Validate Agent before relying on a newly built agent in production chats.
  • Delete Agent is permanent — confirm the agent id and project first.
  • MCP secrets (API keys, Authorization headers) are stored via the platform secrets path, not as plain text in the agent JSON.
  • For day-to-day chat with an existing agent, you do not need Agent Manager on that agent — use it on the build side only.

​
Troubleshooting