Sharing and collaboration

You’ve built an agent. Now you want someone else to look at it, edit it, or ship it with you. There are three ways to do that in BuildBot — pick the one that matches what you’re actually doing.

What you want	The right tool
Show your work to someone (read-only)	Private link
Get a one-off edit from a contractor or peer	Export → edit → re-import
Build agents alongside other people	Invite them to a workspace

A private link is the right choice when you want someone to see your work but not change it: a review request, a blog post reference, “look at this thing I built”.

To share an agent or project:

1. Open the agent or project in the builder
2. Click Share
3. Click Create share link
4. Copy the URL and send it to whoever should see it

Anyone with the link can view the agent or project, including its full instructions and files, and download it for their own platform. They cannot edit it. The page isn’t listed anywhere or shown in search results. API keys and other credentials are always hidden, and nobody can see your workspace, its members, or your other content.

You can revoke a link at any time from the same dialog; anyone with the URL loses access immediately.

When someone with an account opens a shared agent, they’ll see Fork into my workspace. It copies your agent into their workspace as a starting point for their own work. They can edit their copy freely; your original is untouched. Shared projects can be viewed and downloaded, but not forked.

You need a freelancer to fix one thing in your agent, or a friend who knows prompt engineering wants to take a pass at your rules. For a one-off, you don’t need to give them access to your workspace — exports are designed for exactly this.

1. Export the agent or project. Click Export in the builder and choose a format (Claude Code or Cursor). You’ll get a downloadable bundle with everything the agent needs: rules, skills, hooks, MCP definitions.
2. Send the bundle to your collaborator. Email it, drop it in a shared folder, push it to a Git repo — whatever works. The bundle is a self-contained set of files.
3. Your collaborator edits it. They can edit the files directly or load the bundle into their own BuildBot workspace using the import flow.
4. Re-import the bundle. Back in BuildBot, click Import and select the bundle they send back. You can review what’s new before you commit it; items that already exist are skipped rather than duplicated.

• One-off edits where you don’t need the collaborator in your workspace
• Working with someone who isn’t on BuildBot yet — they can edit the raw files directly
• Keeping clear ownership: the agent stays yours, your collaborator’s involvement is bounded

Export → edit → re-import is great for occasional collaboration. It starts to feel heavy when:

• You’re going back and forth more than two or three times
• Several people need to make changes
• You need permission boundaries (some people can edit, others only review)

Once any of those is true, invite them to the workspace.

Open Settings → Workspace → Members, then Invite member, and enter their email. Each person gets a role in that workspace only:

• Viewer — read everything in the workspace
• Editor — create and edit content
• Admin — manage members and workspace settings

Owners and admins of your organization are admins of every workspace in it automatically.

Workspaces in your personal organization share view-only access: people you invite there join as Viewers. To collaborate on editing, use a team organization. In a team organization’s workspaces, people from outside the team can be at most Editors.

An invitation expires after 14 days. Inviting someone to one workspace gives them no access to your other workspaces or to your billing, and you can remove them at any time. People from outside your organization are shown as an Outside collaborator. Outside collaborators can’t publish share links, but they can create API keys for the workspaces they belong to.

Every workspace belongs to an organization, which owns it and pays for it. See Organizations and workspaces for how accounts, organizations and workspaces fit together, including team organizations.

• “I want a friend to see this agent I built” → Private link
• “I want a freelancer to clean up my prompts once” → Export → edit → re-import
• “I want my coworker to be able to edit this whenever” → Invite them as an Editor to a team organization’s workspace
• “I want a client to review our agents without changing them” → Invite them as a Viewer
• “I want to start from someone else’s agent” → Open their link and click Fork into my workspace