Publishing an Agent

Overview

Publishing freezes your agent’s current state into a versioned, shareable release. The draft itself stays editable - publishing never affects work in progress.

When you publish, you choose visibility, set a version, and add release notes. Public agents go through a quick marketplace review before they appear at /public/agent/{id}.

Note

Who can publish. You publish agents you created. Public needs you to be an Owner or Admin of the organization; this works on any plan, including Free Personal. A Member can publish their own agent to Organizational or Private only, and only while the organization has an active paid plan (Pro, Team, or Enterprise). See Plans and Roles & Permissions.

Visibility

There are three visibility options:

• Private - only you and people you share the link with can use the agent. Useful while you iterate.
• Organizational - visible to everyone in your organization, but not listed publicly. Good for an internal helper the whole team can use.
• Public - listed on the Agent Marketplace and discoverable by anyone on Rival.

Visibility is set per version. You can keep one version Private or Organizational while another stays Public.

Sharing with a team

Publishing isn’t the only way to let colleagues use an agent. An Owner or Admin can add the agent to a team from Settings → Teams, on the team’s Agents tab. Everyone on that team can then open it, and their team role decides what they can do:

• Executor - chat with the agent and authorise their own connectors for it, but not change it.
• Editor - all of that, plus change its instructions, tools, knowledge, rituals, and schedules.

This works on the draft agent, with no publish needed, so it’s the right choice for an agent a team maintains together. See Teams and Roles & Permissions.

Versions

Versions follow semantic versioning - pick the bump type when you publish:

Bump	Use when	Example
Major	Breaking changes to behavior	1.2.3 → 2.0.0
Minor	New capability, backward compatible	1.2.3 → 1.3.0
Patch	Small fixes and tweaks	1.2.3 → 1.2.4

Older versions stay available for anyone already using them. Versions are immutable - if you need to change something, publish a new version.

Release notes

A short description of what changed in this version. Adopters see release notes on the listing’s changelog, so write them with the person using the agent in mind:

• Added a “follow-up” tool so the agent can send reminders.
• Tightened the persona - agent is now more concise.
• Fixed: ritual was running an hour early.

For your first publish, “Initial release.” is fine.

The publish flow

1. Open the agent editor and click Publish.

2. Choose Private, Organizational, or Public visibility.

3. Pick a version bump (Major / Minor / Patch). The next version number is computed for you.

4. Write release notes - or use the auto-generated draft as a starting point.

5. Confirm. If you chose Public, the listing is queued for marketplace review.

Marketplace review

Public agents don’t appear at /public/agent/{id} immediately. After you click Publish, the listing goes into a review queue. When the listing is approved, you get an email notification confirming it’s live.

If something needs to change before approval, you’ll get an email with the reason - fix the agent, edit your listing copy, and publish a new version.

Part of the check is automatic: after you publish, Rival runs the agent’s eval tests, a safety baseline, and your showcase prompts, and emails you the verdict.

Note

Private versions skip the review queue and are usable immediately. Only Public visibility triggers review.

What happens after publishing

• A new immutable version is created and listed in the Versions panel on your agent.
• For Private: the version is usable right away by anyone with the link.
• For Public: once approved, the listing appears at /public/agent/{id} and on the Agent Marketplace grid.
• Your draft remains exactly as it was - you can keep editing without affecting the published version.

Listing, unlisting, and versions

• Update - publish a new version. The old one stays available; adopters on the old version are unaffected.
• Unlist - unlisting a public version takes it off the Agent Marketplace so it stops appearing in search and the grid. Adopters who already pulled the agent into their org keep their copy.
• Re-list - set a version back to Public to return it to the Marketplace; it goes through review again.

There is no “edit a published version” - versions are immutable by design. To change behavior, publish a new version.

Next steps

• See your published agent on the Agent Marketplace
• Sell it as a subscription instead of a one-time fee
• Iterate on the draft and publish a new version when you’re ready
• Watch schedule logs and chat feedback to spot issues early