Skip to main content

Install the CLI

The rtk CLI is what actually saves the tokens. Install it on every developer machine.

1. Install​

curl -fsSL https://github.com/rtk-ai/rtk-pro-releases/releases/latest/download/install.sh | sh

You can also download a binary manually from your dashboard under Settings → Install RTK Pro.

:::note Platforms Linux (x86_64 and aarch64) and macOS (Intel and Apple Silicon). On Windows, use WSL2. :::

2. Hook your AI tool​

rtk init --global

This installs a hook into Claude Code (and compatible tools) so everyday commands are automatically routed through rtk. Nothing changes in how you work — output just gets lighter before reaching the AI. Desktop users can use the RTK Launcher app, which applies the hook for Claude Desktop automatically.

3. Connect to your team​

rtk login --endpoint https://<your-team>.cloud.rtk-ai.app

Use your team's workspace URL — the address you open the dashboard at. This signs you in as yourself, so your usage is attributed to your account (needed for the By developer charts). The license activates automatically on sign-in.

Two ways it can authenticate you:

  • Device code (default) — the CLI shows a short code and a URL; open the URL on any device where you're already signed in to the dashboard, approve the code, and the CLI picks up your session. This is the default on every machine, including headless / SSH / WSL. The code expires after 10 minutes.
  • Browser sign-in (add --browser) — opens a browser to complete the sign-in on a local loopback and hands the session back to the CLI. The browser flow currently supports Google only; use the device-code flow for GitHub, Microsoft, or company SSO.

Because sign-in is SSO-only, you approve the login with your identity provider — there's no password to type at the CLI. The CLI stores a token tied to your account (not a shared one), so every event you generate is attributed to you.

:::tip CI machines use an agent token instead For pipelines and shared runners — where there's no individual developer to attribute to — an admin creates an agent token (Dashboard → Admin → Agent tokens; starts with rtk-agent-, shown once). Agent-token usage is org-level and shows up as "agent"/"Anonymous" in per-developer views — that's expected for CI. Use personal rtk login on developer machines to get real per-developer breakdowns. :::

4. Check it works​

Confirm you're connected — run:

rtk cloud-status

…or check the connection status dot in the dashboard sidebar. Then run a normal session through your AI tool and watch your team dashboard: within a few minutes, metrics start appearing as they're ingested.

:::note Privacy rtk reports token counts, command names and metadata — never your code or command output. Secret redaction happens on your machine (see Shield); plaintext secrets never leave it. Your admin can additionally hide developer identities in analytics. :::