Command Palette

Search conversations, projects, playbooks, and more

Agent identities

Give a project an agent teammate with its own email address and Slack handle.

An agent identity belongs to a project and has its own email address and optional Slack handle. In Slack, it answers when @mentioned in-thread with project context. For active identities, email is an intake channel: messages are captured for review, but the agent does not reply by email.


Prerequisites

To use Slack, connect your workspace first: Settings → Integrations → Slack in the dashboard. This installs the crewkit Slack app for your organization; individual agents get handles within that workspace. Email does not require a Slack connection.


Create an agent

Go to Projects → your project → Team Agents and create an agent:

  • Name — how the agent is identified in crewkit
  • Email handle — the agent's address under agent.crewkit.ai
  • Slack handle and workspace ID — how teammates @mention it
  • Default Slack channel (optional)
  • Display name and avatar (optional) — override how it appears in Slack

Mention it in a thread

@mention the agent in any Slack thread and it replies in-thread, drawing on the project's institutional memory — uploaded docs, conventions, prior sessions. The conversation stays where your team already works.

Messages directed at the agent are also captured as project artifacts. Untrusted inbound content waits in the Inbox until a human confirms it before it can be injected as context.


Lifecycle and credentials

Each agent has a status — active, paused, or archived — so you can take one offline without deleting it.

Credentials can be rotated at any time from the agent's row on the Team Agents page. Rotation invalidates the old credentials immediately.


Use project email

Open the project overview and find Project email to see every agent identity's full address. You can copy an address or choose Download contact card to import it into your contacts.

Mail sent to an active address creates an untrusted, non-injectable artifact. It waits in the Inbox until a human confirms it before it can enter agent context. The message receives no email reply from the agent. Paused and archived identities keep their addresses and contact cards, but those addresses do not accept or capture inbound mail.


Next steps

  • Artifacts and project memory
  • Team management
  • Session sharing

Blueprints

A living project plan — epics and tasks linked to the real conversations that did the work.

MCP server

Expose your project's institutional memory to any MCP-capable agent with crewkit mcp serve.

On this page

PrerequisitesCreate an agentMention it in a threadLifecycle and credentialsUse project emailNext steps