download dots
Publish Agents Publicly

Publish Agents Publicly

Updated 2026-05-06·5 min read
On this page (9)

Overview

Publish any Taskade AI agent to a public URL so customers, prospects, or community members can chat with it directly. You decide which tools the agent can call when used by anonymous visitors and which projects feed its context. Everything else stays private inside your workspace.

TL;DR: Open an agent, click Share then Public, pick a URL slug, and turn on public access. The agent becomes reachable at taskade.com/a/{slug} immediately. Customize the theme, header, and suggested prompts from the same panel. Pair public agents with Agent Widgets to embed the chat on a website, and read every conversation in your Agent Inbox.


Publish an agent

Open the agent in the Agents tab, then turn on public access.

  1. Open the Agents tab in your workspace or folder.
  2. Click the agent you want to publish.
  3. Open Share in the top-right.
  4. Switch to the Public tab and toggle Public access on.
  5. Choose a URL slug (for example, support-bot).
  6. Click Save.

The agent is reachable at taskade.com/a/{slug} immediately. Send the link, drop it into a Notion page, or post it in your community.


Customize the public surface

The Public tab lets you shape how anonymous visitors experience the agent.

  • Theme: light, dark, or auto.
  • Brand color: pick a hex code for the launcher and accents.
  • Header and title: custom welcome heading instead of the default agent name.
  • Suggested prompts: starter questions that nudge visitors to ask the right things.
  • Hide Taskade branding: clean popout on Business and above.
  • Message layout: bubble, transcript, or compact.

Changes save instantly. The public surface picks them up on the visitor's next load.


Knowledge scoping for public chats

Public agents only see the knowledge sources you have explicitly attached to the agent. The Knowledge panel is the source of truth: anything connected there is fair game for public answers; anything outside the agent stays private. Connect a public FAQ project, leave the internal CRM out, and the agent answers from the right material every time.

For sensitive content, build a separate public-facing agent with its own knowledge connections instead of toggling sources on and off in real time. That keeps the security model simple. See Agent Knowledge & Memory for the full setup.


How a public agent fits Workspace DNA

A public agent is the public-facing tip of your Workspace DNA. It draws Memory from the Projects you connect, runs Intelligence with the agent's prompt and tools, and triggers Execution through whichever automations it can call.

Anonymous visitor Public agent Memoryconnected Projects + knowledge Executiontools + automations Public Inboxevery conversation logged

Anything you do not connect to the agent stays internal. That is the security model in one picture.


Public Inbox

Every public conversation lands in the agent's Inbox. Read it like a chat support log, reply, or hand off to a teammate.

  • Open the agent.
  • Click Chat in the top-right.
  • Switch to the Inbox tab in the left sidebar.

You'll see every public thread grouped by visitor, with the original prompt and the agent's full response. Reply manually, or wire up an automation to forward unresolved threads to Slack, email, or a CRM ticket. Read Agent Inbox for the full setup.


Rate limits and abuse controls

Public agents come with safeguards out of the box.

  1. Free conversations are capped per visitor, so a single user can't drain your AI credits in one session.
  2. Signed-in conversations consume the workspace credit pool, governed by your plan.
  3. Every public agent has a per-IP throttle that blocks rapid-fire bot traffic automatically.
  4. You can pause public access in one click. The link returns 404 instantly, and you can resume any time.

Plan-level credit caps apply at the workspace level, so a viral public agent never silently overdraws.


When to make an agent private again

Switch the Public access toggle off and the public URL returns 404 immediately. Knowledge connections, tool configurations, and conversation history all stay intact, so you can flip the agent back on later without losing setup.

This is useful for:

  • Limited-time campaigns. Publish for a launch week, then take it down.
  • Iterating in private. Pause, retrain, re-enable.
  • Compliance reviews. Take an agent offline, audit, and restore.