Sharing teams and agents

You can share a team you built, or a single agent, with someone else. Agentbits saves it as a .agentbits file. The other person imports it from the file or from a GitHub link, and sees everything in it before anything is added.

Export

1. Open the unit in Organization → Teams, or the agent in Organization → Agents.
2. In the Share card, click Export and choose where to save the file.

A unit is exported with everything under it. What goes into the package:

• the unit tree (sub-units), with titles and unit leads,
• agent profiles: name, role, job description, expertise, persona (working style) and look,
• the suggested provider type and model of each agent,
• the permissions each agent asks for,
• skill files, without executable files,
• the names of the connections and apps the agents used, as a setup note.

What never goes into it: API keys, connection and app settings, your provider records, tasks, chat, memory, files and local folder paths.

Import

1. Open Organization → Templates and click Import package.
2. Choose a .agentbits file, or paste a GitHub link to one (for example github.com/owner/repo/blob/…/team.agentbits).
3. Read the preview, pick where to add it under Add under, then click Import.

The preview shows each agent’s full job description and persona. Lines that read like instructions to the model are marked “Looks like an instruction to the model — check it”. It also shows which provider each agent will use: one of your providers of the suggested type (your default first), or else your default provider. Connections and apps the package mentions are listed by name; set up your own and grant access.

Warning: Job descriptions and personas become your agents’ instructions. Read them before you import a package from someone you don’t know.

A package is untrusted input, so imports follow fixed rules:

• Imported agents always start with Require approval on and get no extra allowed folders. A package can’t give them more than the permissions it lists.
• If an agent’s name is taken, the imported agent gets a number.
• An imported agent never becomes the organization lead. Unit leads inside the package are kept.
• If a skill with the same name is already installed, yours is kept and assigned instead.
• Executable files are never imported.
• A package can be up to 25 MB. A package made with a newer Agentbits is refused until you update the app.

Packages in private repositories

For a link to a private GitHub repository, add a GitHub token under Organization → Skills (read access to the repository contents is enough). It is the same token Agentbits uses for private skills. See Skills.

What is not available

There is no online gallery of shared teams yet. You share packages as files or GitHub links.

See also Organization and Security.