Slait CLI

Automatically capture your Cursor and Claude sessions and stream them to the Slait dashboard for analysis.

Install

npm install -g slait.dev

Or run directly with npx (no install needed).

Quick Start

Get your API key from your Slait dashboard profile, then run this in your project directory:

npx slait.dev setup <your-api-key>

That single command saves your key, links the project, and installs Cursor/Claude hooks. You're done — sessions appear on your dashboard automatically.

Manual setup

If you prefer to run each step individually:

slait config set-key <your-api-key>
cd /path/to/your/project
slait init
slait hooks install --cursor --claude

How It Works

Once hooks are installed, every Cursor or Claude session in your project is captured automatically:

• Session starts — a live session appears on your dashboard with a green "Live" badge
• Each turn completes — the transcript updates in real time on the dashboard
• Session ends — the full transcript is analyzed (9 AI skill modules scored 0–5) and results appear on the dashboard

No manual uploading required. No background processes. The CLI is stateless — Cursor/Claude hooks invoke it at the right moments.

Commands

slait setup

One-command setup that saves your API key, links the current project, and installs hooks.

npx slait.dev setup <api-key>              # Auto-detects Cursor/Claude and installs hooks
npx slait.dev setup <api-key> --cursor     # Only install Cursor hooks
npx slait.dev setup <api-key> --claude     # Only install Claude hooks
npx slait.dev setup <api-key> --name "App" # Custom project name

slait config

Manage CLI configuration stored in ~/.slait/config.json.

slait config set-key <api_key>    # Save your API key
slait config set-url <url>        # Set dashboard URL (default: https://slait.dev)

slait init

Link the current directory to a Slait dashboard project. Creates a new project on the dashboard and stores the mapping locally.

slait init                        # Uses directory name as project name
slait init --name "My App"        # Custom project name

slait hooks

Manage Cursor and Claude hooks for automatic session capture.

slait hooks install --cursor      # Install Cursor hooks (.cursor/hooks.json)
slait hooks install --claude      # Install Claude hooks (.claude/settings.json)
slait hooks install --cursor --claude  # Install both

slait hooks uninstall --cursor    # Remove Cursor hooks
slait hooks uninstall --claude    # Remove Claude hooks

slait hooks status                # Show which hooks are installed

slait upload

Manually upload a transcript file for analysis. Useful for sessions that happened before hooks were installed.

slait upload ./my-session.jsonl           # Upload a specific file
slait upload --cursor --latest            # Upload most recent Cursor transcript
slait upload --claude --latest            # Upload most recent Claude transcript

slait status

Show the current state of the CLI — API key, linked project, installed hooks.

slait status

Example output:

Slait CLI Status
────────────────────────────────────────
API key:    configured
Base URL:   https://slait.dev

Project:    my-app
Project ID: a266eb86-cd0f-41d7-b969-36d975b3f390
Dashboard:  https://slait.dev/project/a266eb86-cd0f-41d7-b969-36d975b3f390
Linked at:  2026-03-07T01:29:07.974Z

Cursor hooks: installed
Claude hooks: not installed

FAQ

Where is my API key? Go to your Slait dashboard profile page. There's a "Set up Slait CLI" section that shows your key with a copy button.

Will it capture the session I'm currently in? No — hooks only fire for sessions that start after installation. You can manually upload the current session when it's done with slait upload --cursor --latest.

What data is sent? The raw transcript (your prompts and AI responses) is sent to the Slait API for analysis. Analysis runs server-side — no API keys are needed on your machine besides the Slait API key.

Can I use it in multiple projects? Yes. Run npx slait.dev setup <api-key> in each project directory. Each gets its own dashboard project.

How do I unlink a project? Remove the link file:

rm -rf ~/.slait/projects/

Then run slait init again to re-link.

Does it work with Cursor CLI (agent) mode? The stop hook does not fire in headless (-p) mode. It works fully in interactive Cursor sessions (both IDE and interactive CLI).