Public Links
Shareable URLs that let unauthenticated users chat with agents. Supports optional email verification, session persistence, per-user memory, and rate limiting.
Concepts
https://your-domain.com/chat/{token}) that allows anyone to chat with an agent without logging in.(agent_name, user_email). Updated via background summarization every 5 messages.How It Works
Open the agent detail page and go to the Channels tab. Public links live under Distribution → Public links.
Click Create Link. The Create Public Link dialog asks for a Name (optional) and an Expiration (optional) — a date-and-time picker; leave it empty for a link that never expires. An expired link shows Expired on its card and answers visitors with the expired notice; edit the link to move or clear the date. The picker shows and takes the expiry in your browser's local time. Saving the Edit dialog without touching the date keeps the expiry exactly as it was; clearing the field removes it. Email verification and the allow-list come from the agent's access policy on the same tab, and apply across web, Telegram and Slack alike.
Copy the URL from the link's card (the copy icon) and share it. Editing a link later adds a Link enabled checkbox to switch it off without deleting it.
Recipients open the URL. If the agent requires a verified email, they enter their email, receive a code and verify; then they chat. A verification lasts 24 hours in that browser. After that, the link shows the email form again with Session expired. Please verify your email again. If a message was being sent when the session ran out, its text comes back in the input after the visitor verifies. Visitors are never sent to the Trinity sign-in page, and a logged-in Trinity user who opens their own link stays signed in.
Conversations persist — the user can return later and continue where they left off. This holds for anonymous visitors too: reloading the page in the same browser brings the conversation back.
New in the chat header starts a fresh session and clears the previous one.
If the list of links fails to load, the panel says so with Try again; your links are unchanged. A refresh that fails after the list loaded keeps the list and shows a banner with the retry.
If the agent fails to answer a message, the visitor sees one plain line — The agent couldn't respond right now. Your message is back in the box below — send it again to retry. — and their message returns to the input. The technical error stays on the execution for you to read in Executions; visitors never see it. A stop reason, or a notice that a skill is waiting for approval, is still shown to the visitor because it is written for them.
The link shown is always a full URL. It uses the Public URL under Settings → General when one is set (the external_url), otherwise FRONTEND_URL. When neither is set, the Channels tab completes the path with the address you opened Trinity on, so what you copy is a working https://…/chat/{token} URL rather than a bare /chat/{token} path. Set a public URL when the address you use internally is not the one outsiders can reach — see Public Access.
Model and Instructions for Public Chats
Two per-agent settings on the Channels tab shape public-link conversations (and channel chats) without touching the agent's core configuration: the Public chat model override and the Additional instructions — public & channel chats only field. Both apply to public links, Slack/Telegram/WhatsApp, and paid chat — never to the owner's own chats or schedules. See Agent Sharing & Access.
Connect Slack from a Public Link
Each public link card has a Slack row with a Connect Slack button (owner or admin only). It is a shortcut into the Slack channel binding described in Slack Integration:
Once connected, the row shows the workspace name and who connected it, with an enable/disable toggle and Disconnect Slack. The Slack conversation follows the same access rules as the link itself.
Chat History for Logged-In Users
When a Trinity user who is logged in opens a public chat link, a history dropdown appears at the top of the chat interface showing their previous conversations with that agent.
API Endpoints
| Endpoint | Method | Description |
|---|---|---|
| /api/agents/{name}/public-links | GET | List public links |
| /api/agents/{name}/public-links | POST | Create a public link — expires_at is an ISO 8601 timestamp (2026-12-31T23:59:00Z), omitted or empty for no expiry; any other value is refused with 422 and nothing is written |
| /api/agents/{name}/public-links/{id} | PUT | Update a public link — expires_at is validated the same way. Sent as null or empty, it removes the expiry; left out of the body, the expiry is kept, so a rename or the enable toggle never clears it |
| /api/agents/{name}/public-links/{id} | DELETE | Delete a public link |
| /api/public/chat/{token} | POST | Send a message via public chat |
| /api/public/history/{token} | GET | Retrieve chat history |
| /api/public/executions/{token}/{id}/status | GET | Poll a turn's status. A failed turn's error is always the fixed line Failed to process your request. Please try again., never the execution's own error. The one exception is a turn the agent will not take from public links (below), which reads This agent isn't taking conversations from public links right now. Please contact its owner. |
| /api/agents/{name}/public-links/{id}/slack | GET / PUT / DELETE | Slack connection status, settings, disconnect |
| /api/agents/{name}/public-links/{id}/slack/connect | POST | Connect Slack: binds a channel, or returns an OAuth URL when no workspace is connected |
Limitations
403 on the direct chat call). See Agent Guardrails → Visitors and the Shell.