crewkit
MarketplaceFeaturesPricingDocsGitHub
Sign InGet Started
crewkitInstallationQuickstartConfigurationTroubleshooting

Usage

TUICLIDashboardAnalytics

Configure

AgentsSkillsRulesCommandsInheritancePlaybooksExperimentsHooksTeamWorkspacesFAQ

API Reference

API OverviewAuthenticationSessions APIResources APIOrganizations APIProjects APIPlaybooks APIExperiments API

FAQ

Frequently asked questions about crewkit

What is crewkit?

crewkit is an observability, governance, and continuous improvement platform for AI-assisted engineering teams. It helps teams using Claude Code manage agent configurations, track session performance, and iterate on what works.

How does crewkit work with Claude Code?

crewkit wraps Claude Code with a CLI and TUI. When you run crewkit code, it syncs your team's agent configurations (agents, skills, rules, commands) from the crewkit platform, launches Claude Code with those configs, and tracks session data (tokens, costs, tool usage, summaries) for your dashboard.

Is crewkit open source?

The CLI is open source and available on GitHub. The dashboard and API are hosted services included with your crewkit plan.

What does crewkit cost?

crewkit is free for individual developers with one project. Team plans start at $49/month for up to 25 members. Enterprise plans with advanced features and dedicated support are available. See our pricing page for details.

What data does crewkit collect from my sessions?

crewkit collects session metadata: token counts, costs, model usage, tool invocations, durations, and AI-generated summaries. Conversation content (your prompts and responses) can optionally be stored as transcripts for review. Organizations can configure privacy settings to control what data is collected and retained. See our privacy policy for current data retention details.

Can I use crewkit without the dashboard?

Yes. The CLI works standalone for agent sync and session tracking. The dashboard provides analytics, team management, and experiment features on top of the CLI data.

How does 3-tier resource inheritance work?

Resources (agents, skills, rules) can exist at three levels: Platform (crewkit-managed base), Organization (team customs), and Project (project-specific). Each level can inherit from the one above, adding its own content. This lets you set company-wide standards while allowing project-specific customization. See the inheritance guide for details.

What is coaching mode?

Coaching mode is a role-based configuration that changes how AI agents interact with junior developers. Instead of writing code directly, agents in coaching mode guide developers step-by-step, ask clarifying questions, and explain concepts. It is automatically applied based on the developer's role in the organization.

How do A/B experiments work?

Create an experiment for any resource (agent, skill, etc.). crewkit splits sessions between the current version (control) and a modified version (variant). Statistical analysis tracks accuracy, cost, and performance metrics. When results are significant, you can deploy the winning variant. See the experiments guide for a full walkthrough.

Does crewkit work with monorepos and multi-repo projects?

Yes. crewkit supports both single-repo projects and workspace projects that span multiple repositories. The CLI auto-detects project structure from git remotes and can initialize workspaces for multi-repo setups. See the workspaces guide for more.

What platforms does crewkit support?

The CLI runs on macOS (Intel and Apple Silicon), Linux (x86_64 and ARM64), and Windows (via WSL or native). Install via Homebrew, cargo, or the install script. See the installation guide for platform-specific instructions.

How do playbooks work?

Playbooks are collections of conventions (coding standards, patterns, and rules) that can be subscribed to at the organization level and assigned to projects. They enforce team standards automatically. Conventions can be extracted from existing code using AI analysis. See the playbooks guide for details.

Is my code sent to crewkit servers?

No. Your source code stays on your machine. crewkit only collects session metadata, configuration files, and optionally conversation transcripts. The CLI runs locally alongside Claude Code.

Can I import existing Claude Code sessions?

Yes. The crewkit sessions import command discovers and imports historical JSONL transcripts from your local Claude Code history, giving you retroactive analytics.

How do I get started?

Install the CLI with brew install crewkit-io/tap/crewkit, then run crewkit code in any project. The CLI handles authentication, project detection, and agent sync automatically. See the quickstart guide for a full walkthrough.

Workspaces

Multi-repo projects for teams with split codebases.

API Overview

Base URL, authentication, pagination, rate limits, and error handling.

On this page

What is crewkit?How does crewkit work with Claude Code?Is crewkit open source?What does crewkit cost?What data does crewkit collect from my sessions?Can I use crewkit without the dashboard?How does 3-tier resource inheritance work?What is coaching mode?How do A/B experiments work?Does crewkit work with monorepos and multi-repo projects?What platforms does crewkit support?How do playbooks work?Is my code sent to crewkit servers?Can I import existing Claude Code sessions?How do I get started?
crewkit

Observability, governance, and continuous improvement for AI-assisted engineering teams.

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