crewkit
MarketplaceFeaturesPricingDocsGitHub
Sign InGet Started
crewkitInstallationQuickstartConfigurationTroubleshootingFAQ

Usage

TUICLIDashboardAnalytics

Collaborate

ArtifactsSession sharingBlueprintsAgent identitiesMCP server

Configure

AgentsSkillsRulesCommandsInheritancePlaybooksExperimentsHooksTeamWorkspaces

API Reference

API OverviewAuthenticationSessions APIResources APIOrganizations APIProjects APIPlaybooks APIExperiments API

Agent identities

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

An agent identity is an agent that participates like a teammate: it belongs to a project, has its own Slack handle, and answers when @mentioned — in-thread, with full project context. Slack is live today; agent email inboxes are coming soon.


Prerequisites

Connect your Slack workspace first: Settings → Integrations → Slack in the dashboard. This installs the crewkit Slack app for your organization; individual agents get handles within that workspace.


Create an agent

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

  • Name — how the agent is identified in crewkit
  • Email handle — reserved under agent.crewkit.ai (email delivery is coming soon)
  • 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.


Email — coming soon

Every agent reserves an address under agent.crewkit.ai at creation. Inbound email delivery is coming soon; when it lands, emailing an agent will work like mentioning it in Slack — captured, confirmed, and answered with project context.


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 credentialsEmail — coming soonNext steps
crewkit

crewkit is the institutional memory and governance layer for AI-assisted engineering: agents work as teammates, prior work is one search away, and every session is attributed to the exact agent version that ran it.

Product

  • Marketplace
  • Features
  • Pricing
  • Documentation

Resources

  • GitHub
  • Changelog
  • Report Issue
  • System Status

Company

  • About
  • Privacy
  • Terms

© 2026 Karibew Inc. All rights reserved.

Command Palette

Search conversations, projects, playbooks, and more