Skip to main content

cc-hub

A hub directory convention and CLI for coding agents launched by cc-connect.

cc-connect bridges Claude Code, Codex and other agents to chat platforms and starts the agent in a work_dir. cc-hub turns that directory into a hub: the agent's home base on your machine, with a persona, memory, and a registry of your projects and remote hosts. Permissions and background work stay with cc-connect and the agent runtime; the hub adds conventions and routing, not another layer of either.

The hub is agent-agnostic. It ships no Claude- or Codex-specific files; on first run the agent creates the pointers its own ecosystem needs (hub-adapt).

Quick start

uv tool install cc-hub
cc-hub init                     # creates ~/.cc-hub
cc-hub doctor

Install from a regular terminal; on Windows not from a shell inside the Claude desktop app (see docs/install.md).

Point cc-connect at the hub (work_dir = "/home/you/.cc-hub", see docs/cc-connect.md) and send the first message. The agent follows BOOTSTRAP.md: names itself, learns who you are, registers projects, adapts to its runtime, and deletes the bootstrap file.

Commands

Command Purpose
cc-hub init [dir] Seed a hub. Existing files are never overwritten.
cc-hub doctor [--fix] [--json] Health checks: budgets, pointers, leftover hooks.
cc-hub update [--dry-run] Refresh framework-owned files; user files untouched; backups kept.
cc-hub env Probe the machine and write ENV.md / env.json.
cc-hub memory log|search|recent Daily logs and long-term memory.
cc-hub projects list|show|add|remove Registry of local project directories.
cc-hub hosts list Registry of remote machines; the agent connects with ssh itself.
cc-hub link <src> <dst> Symlink, junction or copy (platform decides).

Hub layout

~/.cc-hub/
├── AGENTS.md  AGENTS.local.md  BOOTSTRAP.md      instructions
├── SOUL.md  IDENTITY.md  USER.md                 persona and user
├── MEMORY.md  memory/YYYY-MM-DD.md               memory
├── projects.toml  hosts.toml  hub.toml           registries and config
├── skills/  cron/  scripts/  secrets/            skills, scheduled prompts, your scripts, credentials
└── ENV.md  env.json                              generated state (gitignored)

Framework-owned files (AGENTS.md, BOOTSTRAP.md, skills/hub-*, cron/README.md) are replaced by cc-hub update. Everything else is yours.

Documentation

中文说明见 README.zh-CN.md。

License

MIT

Metadata

Release files for cc-hub 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cc-hub 0.2.1
File Size Uploaded
cc_hub-0.2.1.tar.gz 145.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for cc-hub 0.2.1
File Interpreter ABI Platform
cc_hub-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 184.2 kB

Release files / cc_hub-0.2.1.tar.gz

Download URL cc_hub-0.2.1.tar.gz
Size 145.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9ec0bc81be6642a84efe70abe059b0d6ab813c149ef0a8d0c1795c6d5624b21d
BLAKE2b-256 checksum
How to use checksums
8be6e5eca34c4c5a88dd0b1e1a3a53cd517451e3e7194e0e594631db3a58b293
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.

Transparency log

Release files / cc_hub-0.2.1-py3-none-any.whl

Download URL cc_hub-0.2.1-py3-none-any.whl
Size 38.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
344b7251b0a78f69f992359d3cf1ba49f291f5f18e8e8c10fe10eee808717b45
BLAKE2b-256 checksum
How to use checksums
6bb2e11f2e78f1a12fb7e8d70fbae2b4d1ce1079e57a4a453d607a17850381b7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page