Pick the path that matches why you are here. Each one takes a few minutes and ends where you can see crewkit working.
A developer
- Install the CLI.
- In a repository of one of your organization's projects, run
crewkit code. If you are not signed in, crewkit opens your browser to sign in and the CLI picks up the token. - The first time, crewkit shows its acceptable-use policy and asks you to accept it. A launch that has not accepted it stops there.
- crewkit matches your git remote to a project, syncs your team's agents, skills, commands and playbooks into
.claude/, and launches Claude Code. - When the session ends, open the dashboard: your conversation is in that project's Conversations, with its cost, tokens, tools and summary.
The Quickstart has the detail of each step.
A manager
- Invite your team from Team, choosing each person's role. A Developer runs sessions; a Viewer reads. The roles table lists what each role may do and which conversations it reads.
- Each invited developer follows the developer path above. Their conversations appear in the project they ran them in.
- Cost and usage are under Analytics, for the organization and per project. See Analytics.
- How much of each session crewkit collects is your organization's capture mode. An organization that never set it is on
structured, which stores prompt and response text. An org admin changes it.
An admin
- Choose the capture mode and the retention term in Settings → Organization → Privacy & Telemetry. Both apply to every project in the organization. See Capture modes.
- Connect your tools under Settings → Integrations.
- Set up single sign-on and SCIM, if your organization uses them. See Single sign-on and SCIM.
- Check who has which role on Team. See Team.
Someone sent a link
Someone shared a crewkit page with you: a set of questions to answer, a conversation to read, or a feedback panel in an app. Sent a link says, for each, what it is, what you can do with it, who reads what you send and how long it is kept.