ACP Gateway
Your agents, on your computers — available from Telegram, CLI and MCP.
ACP Gateway connects a central dispatcher to agents running on your PCs. Choose an agent and a dialogue, send a task, review approval requests and receive the answer without opening a remote desktop.
Install · Documentation · Roadmap
How it works
flowchart LR
Telegram --> Dispatcher[ACP Gateway dispatcher]
CLI --> Dispatcher
MCP --> Dispatcher
Dispatcher <--> Home[Home PC · connector + agent]
Dispatcher <--> Work[Work PC · connector + agent]
Connectors initiate the connection to the dispatcher. The agents execute tasks on their own computers; the dispatcher routes messages, results and approvals. Hermes Desktop and Goose integrations are described in the documentation.
What you can do
- Work with agents on multiple PCs through one Telegram bot.
- Create and switch dialogues, retrieve saved answers and handle approvals.
- Choose available models and execution modes when supported by the agent.
- Use the CLI or MCP interface alongside Telegram.
- Install the same package as a dispatcher or connector, with separate setup sections.
Install
Install uv, then:
uv tool install --python 3.12 "acp-gateway==0.2.1"
uv tool update-shell
acpgw setup
The current release is 0.2.1: one dispatcher, outgoing connectors from your PCs, Telegram dashboards and approvals, managed updates and an optional independent companion for updates from Telegram. See project status and the 0.2.1 upgrade instructions.
Follow the Ubuntu dispatcher + Windows/Hermes guide (Russian) for enrollment, connection, Telegram and autostart. For an existing installation, use the update and recovery guide.
To run the dispatcher in Docker on your VPS — behind the reverse proxy you already have, with your own nginx, or by moving a native dispatcher into Docker without re-enrolling computers — see the Docker dispatcher guide (Russian).
Explore
| I want to… | Start here |
|---|---|
| Set up Telegram | Bot setup and commands |
| Run the dispatcher in Docker on a VPS | Docker dispatcher (Russian) |
| Understand support and limitations | Project status |
| Configure a different deployment | Documentation index |
| Develop or build from source | Development guide |
| See what comes next | Roadmap and queue |
License
Metadata
Release files for acp-gateway 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| acp_gateway-0.2.1.tar.gz | 976.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acp_gateway-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / acp_gateway-0.2.1.tar.gz
| Download URL | acp_gateway-0.2.1.tar.gz |
|---|---|
| Size | 976.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30afe36a9c00d2c9ed2a527169e24606694c9b96313d1fbd3149f20be4272d49
|
|
BLAKE2b-256 checksum How to use checksums |
382078a824d1135d9bc74b378853ad7b1ae0c16b81b2f585e60d9d8c7bcc09b2
|
| 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 16, 2026.
Transparency logRelease files / acp_gateway-0.2.1-py3-none-any.whl
| Download URL | acp_gateway-0.2.1-py3-none-any.whl |
|---|---|
| Size | 273.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41cb9723d0a7fcbaae59bfa34a0366a098c07507c45af9786f2aa24ccb971f1a
|
|
BLAKE2b-256 checksum How to use checksums |
c879d1b1941cd13915e319b5fed3dce5baa51b4f60079ddd2eb70a9cbcf04f6d
|
| 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 16, 2026.
Transparency log