ccmd 2.0 — Agentic Project Hub
Pick a project. Pick an agent. Launch.
██████╗ ██████╗███╗ ███╗██████╗
██╔════╝██╔════╝████╗ ████║██╔══██╗
██║ ██║ ██╔████╔██║██║ ██║
██║ ██║ ██║╚██╔╝██║██║ ██║
╚██████╗╚██████╗██║ ╚═╝ ██║██████╔╝
╚═════╝ ╚═════╝╚═╝ ╚═╝╚═════╝
project hub · v2.0
ccmd is a local control plane for coding agents — Claude Code, Grok Build, Codex, Cursor Agent, Goose, Aider, and ChatGPT (browser). It is not another coding agent. It prepares the room and opens the door.
Install
pip install -e .
# or: pip install ccmd (when published)
ccmd doctor
ccmd migrate --apply # import 1.x shortcuts + custom commands
ccmd # vibrant TUI
Python 3.11+.
Daily use
| Command | What |
|---|---|
ccmd |
Project hub TUI |
ccmd open flow --agent claude |
Headless launch |
ccmd list |
Projects |
ccmd agents |
Detect installed agents |
ccmd sessions |
Launch history / kill |
ccmd ssh import |
Pull hosts from ~/.ssh/config |
ccmd aliases import |
Pull aliases from ~/.bashrc |
ccmd mcp |
Stdio MCP tool server |
ccmd doctor |
Paths + agent diagnostics |
TUI keys
↵ open · a agents · n new project · s sessions · h ssh · / filter · q quit
Config
| Path | Role |
|---|---|
~/.ccmd/config.toml |
Global |
~/.ccmd/projects/*.yaml |
Registry |
~/.ccmd/ssh/hosts.yaml |
SSH profiles |
~/.ccmd/aliases.yaml |
Aliases + PATH |
~/.ccmd/sessions.jsonl |
Sessions |
Override home with CCMD_HOME.
MCP
ccmd mcp
Tools: projects.list, projects.get, agents.list, agents.launch, sessions.list, sessions.kill, ssh.list.
NDJSON on stdio (works without the optional mcp package).
Security
- No shell-function-per-command /
eval cd(removed from 1.x) - Subprocess argv lists only
- SSH IdentityFile paths only — never private key contents
- Env file secrets redacted from MCP payloads
- Atomic config writes mode
0600
Migrate from 1.x
ccmd migrate # dry-run
ccmd migrate --apply # write projects + aliases, backup to ~/.ccmd/legacy/
Your go X >>> claude customs become projects with default_agent: claude.
Dev
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest -q
ccmd doctor
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for ccmd 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ccmd-2.1.0.tar.gz | 43.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ccmd-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.2 kB
Release files / ccmd-2.1.0.tar.gz
| Download URL | ccmd-2.1.0.tar.gz |
|---|---|
| Size | 43.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9558e84f4fa59202434824dc069cdc7179635907c6be6520e5b400c4ded1edf7
|
|
BLAKE2b-256 checksum How to use checksums |
e9ed43cd84804126ddda0348bf372184df1a334497002c2dc4768c84d31944ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / ccmd-2.1.0-py3-none-any.whl
| Download URL | ccmd-2.1.0-py3-none-any.whl |
|---|---|
| Size | 54.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b1c384dbaacfbf43da2e3dbc55e96691a4d4daa575b53ccecf3d10a6204c3e5
|
|
BLAKE2b-256 checksum How to use checksums |
e1ad5b5e32f31060a437b106490988063d8598704edcf12016ea5bb77ba064bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for ccmd 2.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
