Skip to main content
A team-shared custom agent is an agent its owner makes available to active members of their current Neo team. Team sharing is private to that team. It does not publish the agent to the public Community Agents directory.

​
Share an agent

Ask Neo to share an agent you own:
Neo changes the agent’s visibility to team. The API determines your current team from your account, so you do not provide a team ID. To share through the API, update the owned agent’s visibility:
Only the owner can edit the shared agent or change its visibility.

​
Install an agent with Neo

Ask Neo to install an agent shared by a teammate:
Neo finds the team-shared source, resolves its source uuid, and installs an independent private copy into your account. A shared source cannot be run directly. After Neo confirms the installation, use the installed agent on your next request:
Neo uses the installed agent ID for that task. You can also ask Neo to list agents shared with your team before choosing one to install.

​
Install an agent through the API

First list team-shared agents:
Use the returned uuid, not the agent slug, to install the agent:
Installation creates an independent private copy owned by the installer. Changes to the shared source do not update installed copies. If the owner later makes the source private, existing installed copies remain private and continue to belong to their installers. You cannot install your own shared agent. Installing the same shared source again returns a conflict instead of creating a duplicate.

​
Stop sharing

Ask Neo:
Or update its visibility through the API:
Making the source private prevents further team discovery and installation. It does not delete the source or copies that teammates already installed.

​
Access rules

  • Both the owner and viewer must be active members of the same team to access the shared source.
  • Team members can discover and install the source, but only the owner can edit or delete it.
  • An installed copy is private, independent, and owned by the installer.
  • Team sharing does not automatically share credentials required by the agent. Share required tools and credentials separately through team-shared custom toolkits, or let each teammate provide their own secrets.
  • Use public visibility when you intend to publish an agent beyond your team. Team visibility is not public publishing.
For complete request and response schemas, see the API reference.