Skip to main content

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.

License: MIT Python 3.12+ PyPI

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.0"
uv tool update-shell
acpgw setup

The current release is 0.2.0, the first stable release: one dispatcher, outgoing connectors from your PCs, Telegram dashboards and approvals, managed updates, and a Docker dispatcher for a VPS. See project status for what is still being accepted.

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

MIT

Metadata

Release files for acp-gateway 0.2.0

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

Source distribution (sdist)

Source distribution for acp-gateway 0.2.0
File Size Uploaded
acp_gateway-0.2.0.tar.gz 879.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for acp-gateway 0.2.0
File Interpreter ABI Platform
acp_gateway-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / acp_gateway-0.2.0.tar.gz

Download URL acp_gateway-0.2.0.tar.gz
Size 879.7 kB
Tags Source
SHA-256 checksum
How to use checksums
9605d7900812331657d0abbea98dda021bfbbff1332a8ee24e081f78b53bac8c
BLAKE2b-256 checksum
How to use checksums
b282b2ebfd4cd08721228845a88c4350246edaf204862078da8b8ef65737db30
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 15, 2026.

Transparency log

Release files / acp_gateway-0.2.0-py3-none-any.whl

Download URL acp_gateway-0.2.0-py3-none-any.whl
Size 233.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3c4b9f56a5e8068dd4579752bd035e20d277a4783699ba13b40e3cdc4f3b3a16
BLAKE2b-256 checksum
How to use checksums
735c18bd5dd724bbce083cdefa4857cfd353323d32fe295d3c2b05d46a271a1f
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 15, 2026.

Transparency log
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