Copera CLI Overview
copera is the official command-line interface for Copera. Use it to work with boards, tables, rows, docs, drive files, channels, notifications, and workspace data — from your terminal or from any script or AI agent.
The CLI is designed for two audiences:
- Power users who prefer the keyboard over the UI, want to script repetitive work, or run Copera from a remote shell.
- AI coding agents (Claude Code, Cursor, OpenCode, Codex, and others) that take real, auditable actions in your workspace on your behalf.
Every action runs as the user behind the token — your permissions are respected, and every change is fully reversible in the app.
Install
macOS / Linux
Run this in your terminal:
curl -fsSL https://cli.copera.ai/install.sh | bash
To install a specific version:
VERSION=0.1.0 curl -fsSL https://cli.copera.ai/install.sh | bash
By default, the installer writes the copera binary to /usr/local/bin/copera. If that directory requires elevated permissions, the script will ask for sudo.
Windows
Open PowerShell and run:
irm https://cli.copera.ai/install.ps1 | iex
You do not need to run PowerShell as Administrator — this installs copera.exe into your user profile.
Close and reopen PowerShell, then verify the install:
copera version
To pin a specific version:
$env:VERSION = "0.1.0"; irm https://cli.copera.ai/install.ps1 | iex
Manual Windows install
If you prefer to download the archive yourself:
- Download the Windows AMD64 zip for the version you want from the Copera CLI CDN.
- Extract
copera.exe. - Move it into a directory on your
PATH, such as%LOCALAPPDATA%\Microsoft\WindowsApps. - Open a new PowerShell window and run
copera version.
From source
If you have Go installed:
go install github.com/copera/copera-cli/cmd/copera@latest
Update
copera update
Use copera update --version 1.2.0 to install a specific version, or copera update --force to skip the confirmation prompt.
First-time setup
For most people, the simplest flow is:
copera auth login
The CLI prints a Copera URL, opens it in your default browser when possible, and asks you to paste the generated token back into the terminal. The printed URL is always available, so the same flow works over SSH, in WSL, or in any terminal where the browser may not open automatically.
If you already have a token, you can skip the browser:
copera auth login --token=cp_pat_xxx
For CI, scripts, and agent pipelines, an environment variable is the cleanest approach:
export COPERA_CLI_AUTH_TOKEN="cp_pat_xxx"
On Windows PowerShell:
$env:COPERA_CLI_AUTH_TOKEN = "cp_pat_xxx"
Try it
Once logged in:
copera auth status
copera boards list
copera docs tree
copera search "onboarding"
For machine-readable output:
copera boards list --json
Next steps
- Authentication — Token types, login flows, and how the CLI resolves credentials.
- Common Commands — Quick reference for boards, rows, docs, drive, channels, search, notifications, and more.
- Configuration — Profiles, default IDs, environment variables, and machine-readable output.