> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pinkfish.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Agents

> Configurable AI assistants with custom instructions, tools, resources, and channels

An **agent** in Pinkfish is a configurable AI assistant. You define how it behaves with instructions, choose which model it runs on, pick the tools it can call (via MCP servers, attached workflows, or other agents), grant it access to resources (datastores, filestores, knowledge bases), and expose it through one or more channels (web chat, Slack, Microsoft Teams, a public URL). You **save** drafts while iterating and **release** published versions that become usable from Coworker.

<img src="https://mintcdn.com/pinkfishai/ZcYFyF2aB9Gj-xv4/images/agents/my-agents-list.png?fit=max&auto=format&n=ZcYFyF2aB9Gj-xv4&q=85&s=186836c83ba884f06d70764e5eef0553" alt="The /agents page showing a list of published agents with status badges, filters, search, and a Create new agent button" width="1440" height="900" data-path="images/agents/my-agents-list.png" />

## What's in this section

<CardGroup cols={2}>
  <Card title="My Agents" icon="table-list" href="/agents/my-agents">
    The `/agents` page — list, filter, search, and monitor all agents in your workspace.
  </Card>

  <Card title="Agent Builder" icon="wrench" href="/agents/agent-builder">
    Anatomy of the builder: tabs on the left, live preview on the right, save and release controls on top.
  </Card>

  <Card title="Instructions" icon="scroll" href="/agents/instructions">
    Name, icon, description, system prompt, model choice, and prompt bubbles.
  </Card>

  <Card title="Tools" icon="screwdriver-wrench" href="/agents/tools">
    MCP connections, embedded services, agents-as-tools, and workflows-as-tools.
  </Card>

  <Card title="Resources" icon="folder" href="/agents/resources">
    Attach datastores, filestores, and knowledge bases with Read / Write / Admin permissions.
  </Card>

  <Card title="Channels" icon="radio" href="/agents/channels">
    Publish your agent to Slack, Microsoft Teams, or a public External URL.
  </Card>

  <Card title="Monitor" icon="chart-line" href="/agents/monitor">
    Replay an agent's chats, inspect tool calls, and debug behavior from inside the builder.
  </Card>

  <Card title="Advanced" icon="sliders" href="/agents/advanced">
    Output Schema — force structured JSON responses when calling the agent via API.
  </Card>

  <Card title="Save & Release" icon="rocket" href="/agents/releases">
    The draft-vs-release model, how releases reach Coworker, and how to roll back.
  </Card>

  <Card title="MCPs" icon="plug" href="/agents/mcps">
    How agents discover and invoke MCP tools from your integrations.
  </Card>
</CardGroup>

## Agent types

Pinkfish supports two agent types:

* **Chat** — A conversational agent that responds to messages. Use for assistants, researchers, and copilots.
* **Workflow** — An agent bound to a specific workflow. Use when you want a workflow run to be triggered conversationally.

Both types use the same builder.

## Where agents run

An agent can answer messages from any of these places once you release it:

* **Coworker** — The chat tab inside Pinkfish. `@`-mention the agent in a Coworker chat.
* **Slack** — Connect a Slack workspace in the Channels tab.
* **Microsoft Teams** — Connect a Teams tenant in the Channels tab.
* **External (public URL)** — A public link that anyone can chat with, with no Pinkfish login.
* **API** — Programmatic access with an agent API key. See [Agent Management API](/api-reference/platform/agent-management).

## How the pieces fit together

<Steps>
  <Step title="Write instructions">
    On the **Instructions** tab, give the agent a name, an icon, a description users will see, a system prompt that defines its behavior, and a model. Optionally add prompt bubbles — one-click conversation starters.
  </Step>

  <Step title="Pick tools">
    On the **Tools** tab, select MCP servers (integrations), Embedded Services, other agents you want this agent to be able to delegate to, and workflows it can trigger. Pinkfish adds a few Auto-selected Tools for every agent.
  </Step>

  <Step title="Attach resources">
    On the **Resources** tab, grant read/write/admin access to specific datastores, filestores, and knowledge bases. Required tools are added to the Tools tab automatically.
  </Step>

  <Step title="Pick channels">
    On the **Channels** tab, enable Slack, Microsoft Teams, or make the agent public via External. A published release is required before External works.
  </Step>

  <Step title="Test in preview">
    The right-hand **Preview** pane is a live chat against your current draft. Click **Information** in the preview to double-check the selected model, tools, and resources.
  </Step>

  <Step title="Save, then release">
    **Save** commits a draft. **Release** publishes an immutable snapshot that becomes available in everyone's Coworker tab (subject to sharing).
  </Step>
</Steps>

## Agent Memory

<Card title="Agent Memory" icon="brain" href="/slash-commands/agent-memory">
  Store and recall user preferences and context across conversations and
  sessions.
</Card>

## Sharing agents

Agents can be shared with other people in your org via the agent's **Share** action. Recipients get access to chat with the agent, but they must connect their own integrations — Pinkfish does not share your OAuth tokens. See the [API reference](/api-reference/platform/agent-management) for programmatic sharing.

## Related features

* **[Coworker](/coworker/overview)** — Where released agents appear for `@`-mention and chat.
* **[Agent Monitor](/orchestration/agent-monitor)** — Org-wide view of every agent chat across all users.
* **[Datastores](/resources/database)**, **[Filestores](/resources/file-store)**, **[Knowledge Bases](/resources/knowledge-base)** — The three resource types you can attach.
* **[API connections](/tools/connections)** — The integrations that feed the Tools tab.