gptme-acp
ACP (Agent Client Protocol) entry point for gptme.
This is a thin shim package that allows gptme to be listed in the ACP agent registry and launched via uvx, enabling agent discovery in editors like Zed and JetBrains.
Usage
Quick start (no install required)
uvx gptme-acp
Persistent install
pipx install gptme-acp
gptme-acp
What this package does
gptme-acp is a minimal wrapper that:
- Declares
gptme[acp]as its dependency (pulls in gptme + theagent-client-protocollibrary) - Exposes
gptme-acpas its default executable — the ACP server that editors connect to
The agent communicates with editors via JSON-RPC over stdio using the ACP protocol.
ACP Agent Registry
This package exists so gptme can be listed in the ACP agent registry:
{
"package": "gptme-acp",
"launch": {"type": "uvx"}
}
The registry powers agent discovery in Zed, JetBrains, and other ACP-compatible editors. Without this package, the registry cannot launch gptme because:
uvx gptmeruns the interactive CLI, not the ACP serveruvx --from 'gptme[acp]' gptme-acprequires--from, a shape the registry cannot express- Extras-qualified specs like
gptme[acp]fail the registry's package-existence check
Configuration
The ACP agent uses gptme's standard configuration (~/.config/gptme/config.toml). API keys are read from environment variables (ANTHROPIC_API_KEY, OPENAI_API_KEY, etc.).
Documentation
Full ACP documentation: https://gptme.org/docs/acp.html
1 maintainer
Release files for gptme-acp 0.34.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 | |
|---|---|---|---|
| gptme_acp-0.34.0.tar.gz | 2.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gptme_acp-0.34.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.4 kB
Release files / gptme_acp-0.34.0.tar.gz
| Download URL | gptme_acp-0.34.0.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0d93b749b5cc37c6248ecb819be23beccaf145a2dee878df38d6c65b7e694d4
|
|
BLAKE2b-256 checksum How to use checksums |
c44279ed56a4d2b55945ae7a04e32e1e586dc1f54d0b522d1ec91dd2d389177c
|
| 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 18, 2026.
Transparency logRelease files / gptme_acp-0.34.0-py3-none-any.whl
| Download URL | gptme_acp-0.34.0-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
576be20a14ee137d0658a4b5825bdd76ca0868ee5b1e194e7530a44483f6389f
|
|
BLAKE2b-256 checksum How to use checksums |
ed7e0bdbe4c00bc78336b3c701d871f6c732774906c0938898f80053ffdede28
|
| 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 18, 2026.
Transparency log
