CHAMPREP CLI overview
The CHAMPREP CLI is the terminal interface to supported CHAMPREP services. It is a local static binary, but every networked command goes through the public API Gateway so the same account, service access, scopes, quotas, and audit controls continue to apply.
Supported workflows
Section titled “Supported workflows”The current CLI includes command families for:
- authentication, profile selection, and your account, plan, and usage;
- Drive files, folders, transfers, and storage usage;
- Mail messages, threads, accounts, and domains;
- Chat rooms and messages;
- Contacts;
- Learn courses and enrollments;
- Notes;
- CHAMPREP AI conversations and usage;
- Meet rooms;
- Calendar events;
- Work boards and tickets;
- CHAMPREP Code projects, bulk cloning, merge requests, issues, pipelines, job logs, runners, and releases;
- Runner Farm accounts, connections, pools, usage, and jobs;
- CHAMPREP QA repositories, scans, findings, quality gates, previews, and IDE workspaces;
- Invoices (list, read, issue, send);
- Forms and responses;
- the organization chart and people search;
- Business (organization) info, members, and usage;
- API-key management, webhook subscriptions, and read-only billing;
- local configuration, shell completion, and version information.
Run champrep --help for the command tree shipped by the installed binary.
That output is authoritative for its version.
Three-step journey
Section titled “Three-step journey”For CHAMPREP Code, Runner Farm and QA, start with Common tasks: clone all your projects or a whole group, set up git credentials, watch pipelines and jobs, manage runners and pools, and gate CI on QA.
champrep auth loginchamprep auth whoamichamprep drive quotachamprep calendar todayGateway-only network model
Section titled “Gateway-only network model”The CLI does not call Drive, Mail, Calendar, AI, or another service backend
directly. It uses the Gateway selected for the active environment. Do not point
CHAMPREP_API_URL at an individual service API; that variable is intended only
for a Gateway-compatible development or smoke-test endpoint.
Interactive and automated authentication
Section titled “Interactive and automated authentication”- Use
champrep auth loginfor a person at a terminal. It opens a browser approval flow and stores the resulting credential in the operating-system keychain. - Use
champrep auth tokento store a scoped API key for longer-lived automation. - Use the
CHAMPREP_TOKENenvironment variable for ephemeral CI jobs where a secret manager injects the key at runtime.
See CLI authentication and API keys for automation before using a credential in a script.
AI agent in the terminal (Eve)
Section titled “AI agent in the terminal (Eve)”eve (or champrep ai / champrep eve) opens Eve, CHAMPREP’s intelligent AI pair-programming and ecosystem agent. Eve works on local code and files with your permission, manages background processes and shells, runs massive multi-agent parallel workflows, and connects with your CHAMPREP cloud services. See
AI agent: Eve (champrep ai / eve).