cc-hub
The home directory for coding agents launched by cc-connect.
A chat-driven agent has three parts: the chat (a bot on Feishu, WeChat, Telegram and others), the bridge that connects the chat to your machine (cc-connect), and a local directory the agent lives in. cc-hub is that directory, the hub: the agent's persona, what it knows about you, its memory, its operating instructions and its skills, plus a small CLI that seeds, checks and upgrades them. It plays the role of an OpenClaw workspace.
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: adapts to its runtime, gets a name, learns how to
address you, registers its scheduled tasks, and deletes the bootstrap file.
Commands
In the table, <…> is a value you must give, […] is optional, and a|b
lists the subcommands of a group.
| Command | Purpose |
|---|---|
cc-hub init [dir] |
Seed a hub. Existing files are never overwritten. |
cc-hub doctor [--fix] [--json] |
Health checks: required files, memory budgets, pointers. |
cc-hub update [--dry-run] |
Refresh framework-owned files; user files untouched; backups kept. |
cc-hub memory log|search|recent |
Daily logs and long-term memory. |
cc-hub link <skills-dir> |
Link every hub skill into an agent's skills directory. |
cc-hub tap add|list|remove |
Register git repositories of apps (taps). |
cc-hub app search|install|list|update|remove|sync|setup-state |
Install, update and remove apps from taps. |
cc-hub cron list|set|reset |
Scheduled tasks: list them, change their times, turn them off or on. |
cc-hub report list|plan|put|send|note|section|language|approve |
Reports: daily to yearly digests that apps add sections to. |
cc-hub feedback [--app NAME] [--json] |
Where to report a problem, with an environment block; sends nothing. |
cc-hub where |
Print the hub directory and the package location. |
cc-hub version |
Print the cc-hub version. |
Examples:
cc-hub cron list # every scheduled task and the time in force
cc-hub cron set plans/morning "0 7 * * *" # run the plans app's morning task at 07:00
cc-hub cron set ledger/prices --off # turn a task off (--on turns it back on)
cc-hub cron reset plans/morning # back to the time the app's file gives
cc-hub cron set report-daily --on # turn the daily report on (08:00 by default)
cc-hub cron set report-weekly "0 20 * * 5" # weekly report on Fridays at 20:00
cc-hub report language zh-CN # write report headings in Chinese
cc-hub report section ledger monthly --off # leave the ledger app out of the monthly report
Quote the cron expression, or the shell splits it. A task's name is its file
name without .md for the hub's own tasks (cron/<name>.md), and
<app>/<task> for an app's. Times you set are kept in hub.toml, so
cc-hub update and app updates keep them; set and reset print the steps
that re-register the task with cc-connect, which the agent runs. Usually you
just ask the agent.
A report is a digest sent to your chat each day, week, month, quarter or year,
with a section from every installed app that adds one (an app's
reports/<period>.md, see docs/apps.md). The five tasks
report-daily, report-weekly, report-monthly, report-quarterly and
report-yearly are off until you turn one on, as above. The headings cc-hub
writes use the language you set (Chinese and English are built in; any other
gets English). A section that runs a command does so only after you approved
that command on this machine; the agent asks during the app's setup and runs
cc-hub report approve <app>, and cc-hub report list shows every period,
section and approval. Sent reports are kept in reports/. While a report is
on, a background task with nothing urgent to say leaves a note
(cc-hub report note) for the next report instead of sending its own
message; when no report is on, it sends its message as before.
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
├── skills/ cron/ scripts/ skills, scheduled tasks, your scripts
├── apps/ apps.lock installed apps and their record
├── reports/ the reports that were sent, one file each
└── hub.toml configuration, task times and report settings
cc-hub update replaces only framework-owned files: AGENTS.md above its
closing marker, BOOTSTRAP.md, skills/hub-*, cron/README.md,
cron/memory-consolidate.md, cron/report-*.md, .gitignore and
.gitattributes. cc-hub app manages apps/ and apps.lock; an app's data,
in the directories it declares, is yours.
Everything else is yours too, including whatever you or cc-connect add below
the closing marker of AGENTS.md.
The hub is a git repository: cc-hub commits what its commands change and the agent commits after each task. See docs/backup.md for a private remote.
Documentation
- Install and upgrade
- cc-connect configuration
- Apps and taps
- Backing up the hub
- Windows notes
- Manual acceptance checklist
- Design spec
中文说明见 README.zh-CN.md。
License
MIT
Metadata
Release files for cc-hub 0.7.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 | Actions |
|---|---|---|---|---|
| cc_hub-0.7.0.tar.gz | 301.3 kB | With provenance | Details for cc_hub-0.7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cc_hub-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for cc_hub-0.7.0-py3-none-any.whl |
Total release size: 404.2 kB
Release files / cc_hub-0.7.0.tar.gz
| Download URL | cc_hub-0.7.0.tar.gz |
|---|---|
| Size | 301.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85fe28c442e6b86004114e116f1d46dee9abb4e8af805682b27ae138f958ee3f
|
|
BLAKE2b-256 checksum How to use checksums |
6449b6186d24c37de71a472ac52b66761b45705ed2d2f70e8e8ec885cfe41959
|
| 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 Oct 19, 2026.
Transparency logRelease files / cc_hub-0.7.0-py3-none-any.whl
| Download URL | cc_hub-0.7.0-py3-none-any.whl |
|---|---|
| Size | 103.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7a4c17026d27d3c9c8090f63d4b81a611e2fab36cb0c504526266f5b34fb9e2
|
|
BLAKE2b-256 checksum How to use checksums |
aff9242eca2f2b6eeab2b829fde719a6c0d794a5975c2587c56cbb6d67e8912a
|
| 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 Oct 19, 2026.
Transparency logSecurity for cc-hub 0.7.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cc_hub-0.7.0.tar.gz
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 Oct 19, 2026.
Transparency logA 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.