Quickstart

Get a fully tracked coding session running in one command.

cd my-project
crewkit code

That's it. crewkit code handles everything inline — authentication, project detection, resource sync, and launching Claude Code.

What happens

Authentication — If you're not logged in, crewkit opens a browser for device auth. You approve on the web, and the CLI picks up the token automatically.
Project detection — crewkit reads your git remote and matches it to a project in your organization. If the project doesn't exist yet, it offers to create one.
Resource sync — Your team's agents, skills, rules, and commands are synced to .claude/ in your project. Files are checksummed so local edits aren't accidentally overwritten.
Launch — Claude Code starts inside the crewkit TUI, which adds a sidebar with real-time metrics.

The TUI

The crewkit TUI wraps Claude Code with a collapsible sidebar showing:

Context — Context window usage, total tokens
Session — Model, duration, turn count, compactions
Git — Branch, uncommitted changes, recent commits
Summary — AI-generated session summary (updates periodically)
Plan — Active plan file tracking

Press Tab to toggle the sidebar. Press Ctrl+C to end the session.

View your session

After the session ends, open the crewkit dashboard to see:

Conversation history with token counts per turn
Total cost and duration
Tool usage breakdown
AI-generated summary and coaching tips

First-time setup

If this is a brand new project, crewkit code handles everything inline. But you can also initialize explicitly:

crewkit init

This walks through project setup interactively — linking your git repo to an organization and project.

For CI/CD environments, use crewkit code --yes to skip interactive prompts. Set CREWKIT_REPOSITORY_ID to specify the repo directly.

Next steps

Get a fully tracked coding session running in one command.

cd my-project
crewkit code

That's it. crewkit code handles everything inline — authentication, project detection, resource sync, and launching Claude Code.

What happens

Authentication — If you're not logged in, crewkit opens a browser for device auth. You approve on the web, and the CLI picks up the token automatically.
Project detection — crewkit reads your git remote and matches it to a project in your organization. If the project doesn't exist yet, it offers to create one.
Resource sync — Your team's agents, skills, rules, and commands are synced to .claude/ in your project. Files are checksummed so local edits aren't accidentally overwritten.
Launch — Claude Code starts inside the crewkit TUI, which adds a sidebar with real-time metrics.

The TUI

The crewkit TUI wraps Claude Code with a collapsible sidebar showing:

Context — Context window usage, total tokens
Session — Model, duration, turn count, compactions
Git — Branch, uncommitted changes, recent commits
Summary — AI-generated session summary (updates periodically)
Plan — Active plan file tracking

Press Tab to toggle the sidebar. Press Ctrl+C to end the session.

View your session

After the session ends, open the crewkit dashboard to see:

Conversation history with token counts per turn
Total cost and duration
Tool usage breakdown
AI-generated summary and coaching tips

First-time setup

If this is a brand new project, crewkit code handles everything inline. But you can also initialize explicitly:

crewkit init

This walks through project setup interactively — linking your git repo to an organization and project.

For CI/CD environments, use crewkit code --yes to skip interactive prompts. Set CREWKIT_REPOSITORY_ID to specify the repo directly.

What happens

The TUI

View your session

First-time setup

Next steps

On this page

Quickstart

What happens

The TUI

View your session

First-time setup

Next steps

On this page

Quickstart

On this page

Command Palette

Quickstart

On this page

Command Palette