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 spaget — pick the one that matches what you’re actually doing.

What you want	The right tool	Plans
Show your work to anyone (read-only)	Public share link	Free, Pro, Team
Get a one-off edit from a contractor or peer	Export → edit → re-import	Free, Pro, Team
Build agents alongside teammates in real time	Team workspace	Team

Public share links are the right choice when you want someone to see your work but not change it. Portfolio links, blog post references, “look at this thing I built” — that’s what these are for.

To share an agent or project:

1. Open the agent or project in the builder
2. Click Share in the top-right
3. Toggle Public link on
4. Copy the URL and send it anywhere

Anyone with the link can view your agent, including its rules, skills, and configuration. They cannot edit it. Sensitive details — credentials for any MCPs, your member list, your other agents — stay private.

If you’re on Pro or Team, you can also add a password or set an expiration date on the link.

When someone views a public share, they’ll see an Import to my workspace button. Clicking it copies your agent into their account as a starting point for their own work. They can edit their copy freely; your original is untouched.

This is how spaget agents spread. If you’ve built something useful, sharing it is the simplest way to get it in front of more people.

You’re on Pro and 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. You don’t need to upgrade to Team for a one-off — exports are designed for exactly this.

1. Export the agent or project. Click Export in the builder and choose a format (Claude Code, Cursor, or Copilot). 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 spaget workspace using the import flow.
4. Re-import the bundle. Back in spaget, click Import and select the bundle they send back. Your agent updates with their changes. You can review the diff before applying.

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

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

• You’re going back and forth more than two or three times
• Multiple people need to make changes simultaneously
• You want a shared history of who changed what
• You need permission boundaries (some people can edit, others only review)

Once any of those is true, it’s time for a Team workspace.

Team workspaces are for groups of people building agents together. You invite collaborators directly, assign them roles (Viewer, Editor), and everyone works in the same workspace in real time.

The differences from a Pro workspace:

• Multiple members with role-based access
• Guests — bring in external collaborators (clients, contractors) without making them part of your organization
• Organization-level features — shared billing, GitHub org integration, SSO (coming soon)
• Unlimited workspaces for organizing work across teams, products, or clients

If you’ve outgrown export-based collaboration, upgrade to Team — your existing Pro workspaces come with you.

• “I want my mom to see this agent I built” → Public share 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” → Team workspace
• “I want to publish this agent in a blog post” → Public share link with public indexing enabled
• “I want to onboard a contractor for a 3-month engagement” → Team workspace, invite as guest
• “I want to fork someone else’s agent to start mine” → Open their public share link, click Import