Circleback CLI
Search and access your meetings, transcripts, emails, calendar events, and more from the terminal, and manage your action items, tags, folders, and meeting access.
Installation
npm install -g @circleback/cli
Requires Node.js 18 or later. The package installs two binaries: circleback and cb (shorthand).
Quick start
# Log in with your browser
cb auth login
# Search recent meetings
cb meetings
# Search by keyword
cb meetings "product review"
# Read by ID (from the meeting URL, e.g. circleback.ai/meetings/abc123)
cb meetings read abc123
# Search transcripts
cb transcripts "pricing discussion"
# Search emails
cb emails "from:[email protected] after:2026-01-01"
# Mark an action item done
cb action-items update 123 --status DONE
# Get raw JSON for scripting
cb meetings --json
Commands
| Command | Description |
|---|---|
cb auth login | Log in to Circleback with your browser |
cb auth login --api-key | Log in with an API key |
cb auth logout | Sign out on this device |
cb update | Update CLI to the latest version |
cb meetings [search] | Search meetings |
cb meetings read <ids...> | Read detailed meeting info, notes, and action items (max 50) |
cb meetings update <id> | Update a meeting |
cb meetings share <id> | Share a meeting or remove access |
cb transcripts <search> | Search transcript content |
cb transcripts read <ids...> | Read full transcripts (max 50) |
cb calendar | Search calendar events |
cb calendar update <id> | Update a calendar event |
cb people <names...> | Search people by name |
cb companies <terms...> | Search companies by name or domain |
cb emails [search] | Search connected email accounts |
cb support [search] | Search Circleback support articles |
cb action-items [search] | Search action items |
cb action-items create <title> | Create an action item |
cb action-items update <id> | Update an action item |
cb action-items delete <id> | Delete an action item |
cb teams | List your workspace and teams |
cb tags | List tags |
cb tags create <name> | Create a tag |
cb tags update <id> | Update a tag |
cb tags delete <id> | Delete a tag |
cb folders | List folders |
cb folders read <ids...> | Read folders |
cb folders create <name> | Create a folder |
cb folders update <id> | Update a folder |
cb folders delete <id> | Delete a folder |
cb folders share <id> | Share a folder |
Run cb --help or cb <command> --help for full usage details.
Meeting identifiers
cb meetings read and cb transcripts read accept up to 50 meeting IDs.
Filtering
Meeting, transcript, and calendar searches support filtering by date range. Meeting and transcript searches also support filtering by tag, person, and company:
cb meetings --tags 1,2 --profiles 42 --domains acme.com
cb meetings --last 30 # Last 30 days
cb meetings --from 2026-01-01 --to 2026-03-01
cb calendar --last 7 # Next 7 days of events
Email search supports inline filter syntax:
cb emails "from:[email protected]"
cb emails "to:[email protected] after:2026-01-01"
cb emails "participant:[email protected] before:2026-06-01"
JSON output
Pass --json to any command to get raw JSON instead of formatted tables. Useful for piping to jq or integrating with other tools:
cb meetings "standup" --json | jq '.[].name'
Login
cb auth login # Opens your browser to log in
cb auth login --api-key # Asks for your API key securely
cb auth logout # Signs out on this device
API-key login links to Settings → API keys, verifies the key, and stores it locally on your device.
For stateless automation, set CIRCLEBACK_API_KEY instead of logging in:
CIRCLEBACK_API_KEY=cb_your_api_key cb meetings --json
Changing meetings, action items, tags, folders, or sharing permissions needs write access. Browser logins from before v0.5.0 don't include it, so run cb auth login again; read-only API keys can't make changes.
An API key limited to one folder only reaches that folder's meetings, transcripts, and action items, so cb --help lists just the commands it can run.
CIRCLEBACK_API_KEY takes precedence over stored credentials. Unset it before running cb auth login; cb auth logout cannot clear an environment variable from your shell.
Agents
The CLI is designed to work well with AI agents and tool-use systems:
- Every command accepts
--jsonfor structured, parseable output - Commands follow a consistent
<resource> <action>pattern - All options have long-form names for clarity
- Error messages include actionable instructions
- Exit codes follow standard conventions (0 = success, 1 = error)