ControlMesh
ControlMesh is a local-first, chat-native task runtime for official coding CLIs. It connects Claude, Codex, Gemini, OpenCode, and configured providers to persistent workspaces, background tasks, multi-agent coordination, messaging transports, and operational tools.
What
ControlMesh lets you:
- work interactively in an enhanced local terminal;
- run the legacy bot runtime through Feishu, Telegram, WeChat, Matrix, and compatible transports;
- create persistent background tasks that can ask for input, resume, recover, and deliver results;
- coordinate bounded multi-agent topologies on a shared Python runtime;
- inspect tasks, providers, events, topologies, and artifacts through a local read-only Web dashboard.
Python remains the authoritative runtime. The TypeScript workspace provides public protocol models, runtime validation, an SDK, and the local dashboard.
Quick Start
Install the released CLI:
pipx install controlmesh
controlmesh
controlmesh opens the enhanced terminal. Use /cm for provider-native mode and /back
to return. Source installs also provide cm as a shell-command alias for controlmesh
(including cm --help and cm --version); older releases may only provide controlmesh.
Start the legacy messaging runtime with:
controlmesh bot
Develop from source:
git clone https://github.com/muqiao215/ControlMesh.git
cd ControlMesh
uv sync --locked --all-extras --dev
uv run controlmesh
Verify the toolchain:
python scripts/doctor_toolchain.py --strict --require-bun
Evaluate the read-only Alpha from an isolated install:
pipx install --suffix=-alpha "controlmesh[api]==0.42.0a1"
controlmesh-alpha api serve
Open the printed local dashboard URL and enter the printed bearer token. The Alpha server
binds only to 127.0.0.1 and exposes read-only /api/v1 routes; see the
read-only Alpha guide for the complete five-minute flow.
Documentation
- Project Context
- Architecture
- Decisions
- Installation
- Read-only Alpha
- Feishu Setup
- Telegram Setup
- WeChat Setup
- Enhanced Terminal
- Full Documentation Index
Contributors and coding agents should begin with AGENTS.md.
Status
The Python terminal, bot, task, provider, memory, transport, and multi-agent runtime is the
stable core. The authenticated /api/v1 facade, TypeScript SDK, and local Web dashboard are
an additive read-only product layer. TypeScript task mutation and runtime replacement remain
blocked until Python golden parity and rollback gates exist.
License
MIT. See LICENSE.
Workflow integration (v0.43.0)
1 maintainer
Metadata
1 maintainer
Release files for controlmesh 0.43.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 | |
|---|---|---|---|
| controlmesh-0.43.0.tar.gz | 2.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| controlmesh-0.43.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 MB
Release files / controlmesh-0.43.0.tar.gz
| Download URL | controlmesh-0.43.0.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c7cbef060b2f0981b7de6a4c8f89ab9db3982c48264774fae8169321a5a36f9
|
|
BLAKE2b-256 checksum How to use checksums |
14bf1afd7a878f250d14cc3ee8dbabfb726d6530657da62f629cdb304b99f40e
|
| 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 11, 2026.
Transparency logRelease files / controlmesh-0.43.0-py3-none-any.whl
| Download URL | controlmesh-0.43.0-py3-none-any.whl |
|---|---|
| Size | 2.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5ab71b5e1944ca5538b3c4d9d2ba4694bf49170f5378108ff6c205233fd0994
|
|
BLAKE2b-256 checksum How to use checksums |
9dec6a7a91bb135ead7b87ec00360e1ece8c6313a539e6db989081ac32013d4b
|
| 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 11, 2026.
Transparency log
