Docs/CLI/Overview
CLI

The cc-* CLI tools

2 min read

DevThrottle ships a small set of command-line tools onto your PATH - the cc-* tools. They exist for your agents as much as for you: an agent that needs to produce a PDF report or a Word document can call a tool that is guaranteed present, instead of improvising a different approach on every machine.

What installs

The installer delivers a deliberately small set - eight tools, each covered command by command in the tool reference:

  • Documents: cc-pdf, cc-html, cc-word - Markdown to a finished PDF, web page, or Word document, and back again.
  • Email: cc-gmail, cc-outlook - read, search, send, and manage mail and calendar from the command line.
  • Images: cc-image - describe a picture, read the text out of one, and resize or convert locally.
  • Vault: cc-vault - a personal store of contacts, tasks, goals, ideas, and documents, with search over all of it.
  • The fleet: cc-devthrottle - your sessions, the messages between them, missions, workflows, skills, schedules, and setup.

Alongside them, the installer manages the apps themselves: the Director, the Gateway, and the Launcher tray app.

Managed, not dumped

Tools are installed and updated by DevThrottle's own setup engine - versioned, hash-checked, and repairable. The Director shows their health in two places: a DevThrottle tools row on the home readiness card, which counts how many of the eight are passing and carries a Fix it button that rebuilds a broken install in one click, and a Tools tab in Settings with a row per tool and what each check found. DevThrottle also repairs a broken tool by itself when it starts, once per run, so most of the time there is nothing for you to notice - and a broken tool install is never a support ticket.

The wider toolbox

The shipped set is the floor, not the ceiling. The open source repository holds a larger collection of cc-* tools - buildable if you are working in the repository, and deliberately not installed: a tool is bundled only once it earns its place, and one that is not bundled is left out of the Tools tab entirely rather than shown as a row you cannot fix. Everything is MIT-licensed and readable in the repository.

Quick check that tools are on PATH
cc-pdf --help
Note
The tools are plain executables on PATH: none of them needs the Director to be running, and they work in any terminal and from any agent. Several do need a credential first - cc-gmail and cc-outlook sign in once with auth, cc-image's AI commands take your account key, cc-vault's search and ask need a model key you supply, and cc-devthrottle's fleet commands run inside a DevThrottle session. The tool reference says which, per tool.