Share and publish

The Share drawer on an agent’s playground controls everything about who can reach it. Its sections are deliberately independent: the agent’s own page, whether it’s listed in Portal, whether chatting requires sign-in, and where it may be embedded are four separate switches, not one.

Your agent’s page

Every deployed agent gets a standalone page on a Guuey-owned name — live since the first deploy, whether or not the agent is listed anywhere. The drawer shows the URL with a copy button as soon as it lands (the default name is claimed a beat after the first Live). Change the name with guuey slug claim from the CLI.

Listing in Portal

Sharing publishes a listing that makes the agent reachable through Portal — its browse surface is the Explore tab, which the drawer calls Discover — with two visibilities:

• List in Discover — anyone can find the agent by browsing Portal’s Explore tab.
• Unlisted link — off Discover entirely; reachable only by its direct link. Safe for any agent.

The share link prefers the agent’s claimed slug and works for both visibilities. Stop sharing (with a confirmation) takes the agent off Discover; the listing keeps its previous visibility so resuming hands out the same URL with the same setting. It does not revoke access — the direct link and the agent’s page keep working for any live agent, listed or not. To actually restrict who can chat, turn on Require sign-in to chat below.

The console’s Distribution tab edits the same listing and access rows under its own names — Publish / Unpublish for the listing, guest access for the sign-in gate — and adds a daily guest message limit Studio doesn’t expose.

The read-only rule for public listing

Public listing is only available for read-only agents — agents with no connected accounts that could modify data. Studio probes the agent’s attached connections and fails closed: while the check is loading, inconclusive, or the agent is write-capable, the public option renders visibly blocked with the reason, and switching an existing unlisted listing to public is refused the same way. An agent that was listed publicly and later gained write-capable tools gets a standing warning recommending a switch to unlisted. Unlisted links have no such gate.

Require sign-in to chat

This toggle is the real access gate — separate from the Discover listing, and it applies to the share link and the agent’s page even when the agent is unlisted:

• Off (default): anyone with the link chats without signing in.
• On: visitors are asked to sign in before chatting.

Changes take effect within about 15 seconds. The gate means “signed-in only”, not a hard guarantee: it is enforced by the agent’s pod, and during a brief backend outage the check fails open, so a guest may slip through.

Listing details

Optional metadata for the Portal listing — it only takes effect once the listing is both public and published:

• Description (up to 4,000 characters) — replaces the agent’s own description on Discover cards and on its detail page in Portal.
• Category (up to 100 characters) — groups the agent under a matching Discover filter chip (exact match — reuse an existing category like the suggestions offered, or it fragments into a new one) and shows as a subtitle on the agent’s detail page in Portal.

You can save details before ever sharing — a metadata save never publishes or changes visibility as a side effect.

Looking for the icon, accent colour, or welcome line? Those brand the agent itself — on its own page and everywhere it’s shared — and they apply whether or not the listing is public. The icon, social-share image, and accent colour live in the console under Agent Settings → General → Branding (or guuey apps update --brand-icon-url); the welcome line is part of the standalone page, under Agent Settings → General → Standalone page (--welcome-copy). The drawer points you there; see Design & distribution.

Embed on your website

For agents whose visitors chat anonymously or on Guuey’s built-in sign-in, the drawer shows a copy-paste embed snippet — a few lines that put the agent on your own site — with an “Advanced options in the console” link beside it. Agents that use your own sign-in don’t get a snippet here: their embed and identity setup live together in the console’s Embed tab, which the drawer links to instead. See Embed for the widget itself and Who the visitor is for the identified-embed setup; how the agent’s own page signs visitors in is Sign-in on the agent’s page.

Allowed origins

The snippet only renders on sites you allow, and the list starts empty — the widget refuses to render anywhere until you add your site, so the whole embed flow completes right here in the drawer:

• Only the exact entry you add is covered — subdomains are not, so list each one separately (https://checkout.example.com).
• For local testing, add localhost with its scheme (http://localhost:3000).
• Saves are validated and normalized; changes reach your site within a few minutes.

Repo-managed access settings

If the agent is reconciled from a repo whose manifest declares access settings (agents as code), the sign-in gate and allowed-origins sections carry the same standing “managed from <repo>” warning as the Settings drawer — the next guuey agent apply overwrites changes made here. A manifest that leaves access alone never touches these settings, so no warning is shown. Listing details are never repo-reconciled.