Docs/CLI/Tool reference
CLI

CLI tool reference

6 min read

Reference for the command-line tools the DevThrottle installer puts on your PATH. They exist so your agents (and you) have a reliable, pre-installed way to produce documents, send email, drive a browser, work with images, keep a personal knowledge vault, and talk to the DevThrottle fleet itself. Every tool answers --help with its full command list.

Document conversion: cc-pdf, cc-html, cc-word

Three converters that turn a Markdown file into a finished document. They share the same option style and the same theme set, so learning one is learning all three.

Usage
cc-pdf input.md -o output.pdf --theme boardroom
cc-html input.md -o output.html --theme paper
cc-word input.md -o output.docx --theme boardroom
cc-pdf input.md -o output.pdf --page-size a4 --margin 1in
  • -o - output file path.
  • --theme - document style (see themes below).
  • --page-size - a4 or letter (cc-pdf only).
  • --margin - page margin, e.g. 1in (cc-pdf only).

The shared themes:

  • boardroom - corporate, executive style with serif fonts; the pick for professional reports.
  • paper - minimal and clean (the default).
  • terminal - technical, monospace.
  • blueprint - technical documentation.
  • thesis - academic.
  • spark - creative, colorful.
  • obsidian - dark theme.

cc-devthrottle

The fleet command surface: talk to your running sessions and Gateway schedules - the same tool your agents use to message each other. The fleet commands call the Gateway with the calling session's own key; every session launched by a Director attached to a Gateway carries that credential in its environment (CC_GATEWAY_URL and CC_GATEWAY_SESSION_KEY) - so run them from inside such a session, or export that pair in a plain terminal first. A local-only Director stamps neither, and the commands say so. Local commands such as setup status and actions work anywhere.

Usage
cc-devthrottle session list
cc-devthrottle message send <id> "message"
cc-devthrottle schedule list
cc-devthrottle setup status
  • actions - list the agent-discoverable actions.
  • session - list, rename, spawn, and manage running sessions.
  • message - send a message to another session, or ask and wait for its answer.
  • settings - read and write Director settings.
  • schedule - list, create, run, enable, disable, and delete Gateway schedules (see Scheduled runs).
  • setup - install, update, and repair DevThrottle.
  • selftest - run the fleet-messaging self-test against the local Director.

Email: cc-gmail and cc-outlook

Read, search, send, and manage email from the command line - one tool per provider, with matching command styles. Both authenticate once (auth) and then work non-interactively, which is what makes them usable by agents.

Usage
cc-gmail list
cc-gmail search "from:someone@example.com"
cc-gmail send --to someone@example.com --subject "Hi" --body "..."
cc-outlook list
cc-outlook reply <id> --body "..."
  • Shared commands: auth, list, read, send, draft, reply, search.
  • cc-gmail adds count, labels, delete/untrash; searches use Gmail query syntax.
  • cc-outlook adds forward, flag, categorize, attachments, download-attachment; auth is Device Code Flow.
  • Both take --account to pick between signed-in accounts.

cc-playwright

Scripted browser automation. It drives a Chromium-family browser (Chrome, Edge, or Chromium) through its debugging port, so clicks and form fills are trusted events that real web apps accept. Multiple isolated browser instances can run at once, each under a named --connection.

Usage
cc-playwright start
cc-playwright navigate --url https://example.com
cc-playwright fill --selector "#email" --value "you@example.com"
cc-playwright screenshot --output page.png
cc-playwright --connection work start
  • Lifecycle: start, stop, status, list.
  • Acting on pages: navigate, click, fill, type, press, select, check, set-files, wait.
  • Reading pages: screenshot, snapshot, info, evaluate, tabs.

cc-image

Image toolkit: AI description and text extraction plus local resize and format conversion. The AI commands run through the DevThrottle API with your dt_ key; the local commands need no key at all.

Usage
cc-image describe photo.png
cc-image ocr scan.png
cc-image resize big.png -o small.png --width 800
cc-image convert image.png -o image.webp
  • describe / ocr - AI analysis and text extraction, single image or whole folders (batch cataloging to JSON/CSV with resume). Requires DEVTHROTTLE_API_KEY.
  • resize / convert / info - local, keyless image operations.
  • Images are downscaled before AI analysis, so bulk runs stay cheap.

cc-vault

A local personal knowledge vault - contacts, tasks, goals, ideas, and documents - with semantic search and ask-a-question retrieval over everything in it. It lives on your machine.

Usage
cc-vault init
cc-vault search "kickoff meeting notes"
cc-vault ask "what did we decide about pricing?"
cc-vault tasks add "Follow up with the pilot customer"
cc-vault backup
  • Entities: contacts, tasks, goals, ideas, docs - each with its own add/list/update commands.
  • Retrieval: search (semantic or hybrid) and ask (question answering over the vault).
  • Care and feeding: stats, backup, restore, link/unlink to connect entities.
Note
Only tools that actually ship in the installer are documented here, on purpose - this page never lists a command your machine might not have. How the toolbox is managed and tested lives in the overview and the Director's Tools view.