The CHAMPREP
command line.

Everything, from your terminal. Drive, Mail, Meet, Notes, AI — one binary, zero lock-in.

macOS · Linux · Windows · Docker | Apache 2.0 · v0.1.0-dev

~ — champrep

$ champrep auth token
✓ Stored token for [email protected] (plan: pro)

$ champrep drive ls /reports
TYPE  NAME            SIZE      MODIFIED
dir   archive/        -         -
file  q4-summary.pdf  2.3 MB    2026-04-10 12:34
file  q4-figures.xlsx 1.1 MB    2026-04-09 18:02

$ champrep ai chat "what changed in Q4?"█

Install

Pick your platform. We detected your OS.

macOS / Linux — Homebrew

brew tap champrep/cli
brew install champrep

Linux / macOS — curl installer

curl -fsSL https://cli.champrep.com/install.sh | sh

Windows — Scoop

scoop bucket add champrep https://github.com/champrep/scoop-cli
scoop install champrep

Any platform — Docker

# Pull the official image from Docker Hub
docker pull champrep/cli:latest

# Verify the install
docker run --rm champrep/cli --version

# Authenticate (stores config in a local volume)
docker run --rm -it \
  -v $HOME/.champrep:/home/champrep/.champrep \
  champrep/cli auth token

# Run commands (reuse the auth volume)
docker run --rm \
  -v $HOME/.champrep:/home/champrep/.champrep \
  champrep/cli drive ls

# Or pass the token directly via env var (CI / scripting)
docker run --rm \
  -e CHAMPREP_TOKEN=cpk_live_xxxxx \
  champrep/cli drive ls /reports

Authenticate

Before running any command, you need to authenticate once. The CLI supports two methods — pick whichever fits your workflow. Both store credentials securely in your OS keychain (macOS Keychain, libsecret on Linux, Windows Credential Manager) — never in plaintext on disk.

Option 1

API Token

Best for CI / automation / scripting

Step 1: Generate an API key in your CHAMPREP account.

Go to champrep.com → Settings → API Keys and click Create New Key. Give it a name, select the services you need (e.g., Drive, Mail, Calendar), and copy the generated key. It starts with cpk_live_.

Step 2: Store the key in the CLI.

$ champrep auth token

Paste your key when prompted. You’ll see:

✓ Stored token for [email protected] (plan: pro)

Step 3: Verify you’re authenticated.

$ champrep auth status

You should see your email, plan, and which services are accessible. You’re ready — every command now uses this token automatically.

Option 2

Browser Login

Best for personal / interactive use

Step 1: Start the login flow.

$ champrep auth login

Your default browser opens to champrep.com/auth/cli with a secure PKCE challenge. No API key needed.

Step 2: Approve the login in your browser.

Sign in with your CHAMPREP account (or use Google / Facebook SSO if configured). You’ll see a confirmation page asking you to approve the CLI. Click Approve.

Step 3: Return to your terminal.

The CLI detects the approval automatically. You’ll see:

✓ Logged in as [email protected]

That’s it — the session token is stored in your OS keychain and every command uses it automatically.

You’re authenticated. Now try a command.

$ champrep drive ls

$ champrep calendar today

$ champrep ai chat "hello"

Need to switch accounts? Use champrep auth list and champrep auth switch <profile>. Need to log out? Run champrep auth logout.

CI / Docker — no keychain needed

In non-interactive environments, skip the keychain and pass the token directly via environment variable:

$ CHAMPREP_TOKEN=cpk_live_... champrep drive ls

# Or in Docker:
$ docker run --rm -e CHAMPREP_TOKEN=cpk_live_... champrep/cli drive ls

One CLI. Every CHAMPREP service.

Same REST surface as the web app — anything you can do in the UI you can script.

Drive

$ champrep drive ls /reports

$ champrep drive cp ~/Videos/demo.mp4 /uploads/

$ champrep drive tree /projects --json

$ champrep drive quota

Upload, download, list, search. Resumable uploads via TUS.

Open Drive →

Mail

$ champrep mail ls --unread

$ champrep mail send --to [email protected] \
    --subject "Q4 report" --body @report.md

$ champrep mail read 42

Send, draft, search and label from the terminal.

Open Mail →

Meet

$ champrep meet create --topic "Q4 review" \
    --start 2026-04-15T10:00

$ champrep meet ls --upcoming

$ champrep meet join abc-defg-hij

Schedule Zoom-powered CHAMPREP meetings, list upcoming, join.

Open Meet →

Notes

$ champrep notes create --title "Standup" \
    --body @notes.md

$ champrep notes ls --json | jq '.[].title'

$ champrep notes read 15

Pipe markdown into rich notes. Tag, search, sync.

Open Notes →

AI

$ champrep ai chat "summarize the Q4 report" \
    --file ~/q4.pdf

$ champrep ai chat "explain this error" \
    --file ~/logs/app.log

Chat, summarize, explain — with file and stream support.

Open AI →

Calendar

$ champrep calendar today

$ champrep calendar week

$ champrep calendar create --title "Team sync" \
    --start "2026-04-15 09:00" --duration 30m

Your day at a glance. Create events, RSVP, time-block.

Open Calendar →

Full CLI reference: API Reference · CLI docs coming soon

Security you can audit.

Keychain-first. Tokens live in macOS Keychain, libsecret, or Windows Credential Manager — never in plaintext on disk.
Redacted logs. Every log path strips Authorization headers before writing.
Scanner-friendly. Tokens carry the cpk_live_ / cpk_test_ prefix so leaks are auto-flagged.
Open source. Apache 2.0 licensed. Binaries are checksummed. Cosign signing on the roadmap.
Profile-bounded. Strict enforcement — one authenticated identity per profile, no accidental cross-account access.

CHAMPREP CLI is Apache 2.0 licensed with checksummed binaries and SBOM manifests for every release.

The CHAMPREPcommand line.