Skip to main content

Connecting the CLI

Once scd-server is running, each developer connects their local scd CLI using a personal CLI token. The admin creates the token in Admin → Users — it is shown once at creation and cannot be retrieved again.

Configure the CLI​

scd configure --central-url http://your-server:3000
scd configure --token <personal-token-from-admin>
scd doctor    # verify connection

scd doctor shows server status, license tier, expiry, and whether the CLI version meets the minimum required version.

Activate the installation​

Run a scan to register this machine with your account on the server:

scd scan

The first scan creates the installation binding. Until this step is completed, the installation shows as Pending first scan in Admin → Users.

Adjust timeouts if needed​

scd configure --server-timeout 30s    # regular API calls (default: 30s)
scd configure --deep-timeout 20m      # deep analysis (default: 20m)

Do not lower the deep timeout — AI analysis on large codebases takes time.

Push local scan history​

If a developer has been scanning locally before connecting, push their existing history:

scd sync --history

This is idempotent — safe to run multiple times.

After connecting​

Every scd scan pushes results to scd-server automatically. No extra commands needed. The team dashboard at http://your-server:3000/dashboard updates after each scan.

Distributed teams​

If your developers are not on the same network, use a VPN to make scd-server reachable without opening an internet-facing port. See Remote access for the full setup guide (Tailscale, WireGuard, Headscale).