@cross-deck/cli — CLI reference

@cross-deck/cli is one binary — crossdeck — with two families. Sign in with your browser and you provision projects and apps, mint keys, and read revenue, analytics, and errors straight from your terminal, across web, iOS, and Android. Or drop the key-based source-map upload into CI, no login, no browser. Same binary, one keychain, honest command names. This page is the full reference.

The launcher

Run crossdeck with no command on an interactive terminal and it opens a session — a working environment, like claude. Inside it you type bare commands with no crossdeck prefix (whoami, init, revenue, use prolend, help, exit), and your active project persists across the session and shows in the prompt. The session opens with the splash — the brand's first impression in your terminal, in two states: logged out shows exactly one path (sign in); logged in reveals the two hats — stand up the engine, then read the facts. The tagline is the honest moat, not a slogan: Crossdeck joins revenue, errors, and identity by identity.

Zero to a running account

The whole journey, word for word — from a machine with nothing installed to a live Crossdeck project with identity wired, a payment rail connected, and the numbers flowing. Follow it top to bottom; every command is exactly what you type and every result is what you'll see. You don't need to be an engineer — where a step happens in your app's code or in the dashboard instead of the terminal, it says so.

npm install -g @cross-deck/cli
crossdeck

prolend ❯ login

prolend ❯ init --name "ProLend" --platform web --domain app.prolend.com

import { Crossdeck } from "@cross-deck/web";

Crossdeck.init({ publishableKey: "cd_pub_live_…" });

// after your user signs in, tell Crossdeck who they are:
await Crossdeck.identify(currentUser.id);

prolend ❯ revenue      # cash coming in, by person
prolend ❯ people       # who you're identifying + their journeys
prolend ❯ analytics    # traffic & where signups come from

crossdeck sourcemaps upload --release v1.0.0 \
  --url-prefix https://app.prolend.com/static/js/ ./dist

That's the whole arc. You just touched several parts of Crossdeck at once — here's what each did:

Two families, one binary

There are two ways to authenticate, for two different callers. Keeping them distinct is deliberate — a human at a keyboard and a CI runner have opposite needs.

Install

A normal npm package. Install it globally for interactive use; use npx in CI so the runner never depends on a pre-installed binary.

Global install

npm install -g @cross-deck/cli

Provides a crossdeck binary on your PATH. Verify with crossdeck --version (prints 1.4.0).

One-shot via npx

npx @cross-deck/cli sourcemaps upload --release v1.2.3 --url-prefix https://app.example.com/static/js/ ./dist

Requirements

• Node.js ≥ 18. Uses the native fetch; no node-fetch dependency.
• One runtime dependency. commander for argument parsing.

Sign in

crossdeck login runs the standard OAuth flow: it opens your browser, you approve on the Crossdeck consent screen, and the CLI receives a short-lived workspace token. Under the hood it's RFC 8252 loopback + PKCE (S256) — the CLI binds a one-shot listener on 127.0.0.1, never sees your password, and never receives a long-lived secret.

crossdeck login

The rotating refresh token is written to ~/.crossdeck/credentials.json with 0600 permissions (owner read/write only). The 1-hour access token is never persisted — every command trades the refresh token for a fresh one and rotates it. See Sessions & sign-out.

Zero to installed — crossdeck init

One command takes a signed-in account from nothing to a working install: it creates a project, creates an app, mints the app's publishable keys, seeds origins (or lets them self-learn), and prints the SDK snippet to paste.

crossdeck init --name "ProLend" --platform web --domain app.prolend.com

Projects & apps

The pieces init orchestrates are also available directly, for adding a second project or a second app to an existing one. All writes go through the audited provisioning gate — the workspace token's scope is the boundary, and every create is recorded.

crossdeck projects

crossdeck apps

crossdeck use

Set — or, with no argument, show — the active project. Every command that takes -p, --project falls back to this, so you set it once and stop repeating yourself.

crossdeck use proj_prolend      # make it active
crossdeck use                   # show the current one

Monitor the REST APIs

The read hat. These call the same /v1 REST APIs your own code would, and print the facts. Every number is self-describing — it carries what it measures and how much it covers — so a count of actors is never quietly reported as a count of customers. Pass --json to get the raw envelope for scripting; omit it for the rendered readout.

Source maps (CI)

The CI family — key-based, no login. Upload .map files from a production build so the dashboard resolves minified frames back to original file:line:function. This is what the Errors tab means by "install the CLI."

crossdeck sourcemaps upload --release v1.2.3 \
  --url-prefix https://app.example.com/static/js/ ./dist

Authenticate with a secret key in an env var — the same CROSSDECK_SECRET_KEY every Crossdeck server SDK reads (or pass -t, --auth-token). The environment (sandbox vs production) is inferred from the key prefix.

The full source-map workflow — bundler config, URL-prefix schemes, running alongside Sentry — lives in the Source maps reference.

Platforms & environments

Crossdeck is multi-platform. The CLI provisions and reads across every runtime the platform supports, and every app carries both a live and a test publishable key so you never mix production and sandbox traffic.

Sessions & sign-out

crossdeck whoami shows the active session — the API it targets, the scopes you were granted, and your portfolio size. crossdeck logout ends the session on this machine.

crossdeck whoami
crossdeck logout

Sign-out is a real revocation, not just a local wipe. crossdeck logout revokes this machine's refresh token server-side (RFC 7009) and then removes the local credential file — so a stolen ~/.crossdeck/credentials.json is dead the moment you log out, not merely absent from your disk.

Help & the command tree

crossdeck help prints the full command tree, grouped by the two hats, in the same premium style as the launcher. crossdeck help <command> (or crossdeck <command> --help) drills into one command's flags.

crossdeck help              # the whole tree
crossdeck help init         # one command's flags
crossdeck init --help       # the same, commander-native

Security

• The key is the boundary. A workspace token carries an explicit scope map. Reads are allowed by scope; every write (create project / app / key) is authorised and audited separately. The CLI never re-implements the gate or widens a token silently.
• No secret ever transits your clipboard. login is browser-based PKCE; the CLI receives a rotating refresh token, never your password and never a long-lived secret.
• Least privilege on disk. The credential file is 0600; the 1-hour access token is never written to disk.
• Revocable everywhere. logout revokes server-side; the dashboard revokes any machine. A lost device is one click from dead.
• CI keys stay scoped. Source-map upload needs only a cd_sk_* secret key; publishable cd_pub_* keys are client-only and are rejected for upload at config-resolve time.

Related

• Web SDK reference — the SDK the CLI provisions keys for.
• Source maps — the full CI upload workflow and bundler config.
• API keys & authentication — publishable vs secret vs workspace tokens, scope, and rotation.
• Create a project — the dashboard equivalent of crossdeck init.
• Source on GitHub — the CLI lives under sdks/cli/.

Last updated when @cross-deck/cli@1.4.0 shipped (Aug 3, 2026). Two families — account (OAuth) and CI (source maps) — one binary.

Using an AI assistant? Read this page as clean markdown — index.md — or the whole docs index at /docs/llms.txt.