wizelit-acp
Stdin/stdout bridge between an ACP-compatible editor and the Wizelit /acp WebSocket.
Editors spawn it via uvx — no separate install step.
Setup
- Install uv:
brew install uv - Add to your editor (replace the hub URL with your team's deployment):
{
"agent_servers": {
"wizelit-hub": {
"type": "custom",
"command": "uvx",
"args": ["wizelit-acp@latest"],
"env": {
"WIZELIT_API_URL": "https://your-wizelit-hub.example.com"
}
}
}
}
- Connect from the editor. On first use, the browser opens for device-link pairing — sign in with Google and Approve.
Credentials are saved to ~/.wizelit/credentials.json. Later connects reuse the token.
How it works
uvxfetches this package from PyPI on first run.- ACP JSON-RPC on stdin/stdout ↔ WebSocket to
WIZELIT_API_URL+/acp. - Agent execution happens on the Wizelit server, not locally.
Optional CLI
uvx wizelit-acp auth login # manual pairing
uvx wizelit-acp auth logout # revoke local credentials
Environment
| Variable | Purpose |
|---|---|
WIZELIT_API_URL |
REST base URL (default http://127.0.0.1:8000) |
WIZELIT_ACP_URL |
Override WebSocket URL |
WIZELIT_CLIENT_NAME |
Pairing label (default ACP IDE) |
WIZELIT_ALLOW_INSECURE |
1 to allow plain http:// / ws:// to non-loopback hosts (not recommended) |
Troubleshooting
| Symptom | What to do |
|---|---|
| Package not found on PyPI | Pin a published version or ask your platform team to release |
uvx: command not found |
brew install uv |
| Browser does not open on Connect | Open the pairing URL in your editor's agent log, or run uvx wizelit-acp auth login |
| Pairing never completes | Sign in with an allowed Google workspace account and click Approve before expiry |
| Auth errors after weeks | uvx wizelit-acp auth logout, then Connect again |
Changed WIZELIT_API_URL (e.g. staging → production) |
Restart the agent; the proxy detects the new hub and re-pairs automatically. Saved credentials are hub-specific and only replaced once the new pairing succeeds |
1 maintainer
Metadata
1 maintainer
Release files for wizelit-acp 0.1.22
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| wizelit_acp-0.1.22.tar.gz | 14.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wizelit_acp-0.1.22-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.5 kB
Release files / wizelit_acp-0.1.22.tar.gz
| Download URL | wizelit_acp-0.1.22.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98f08a4854520a5db6952740fb0ce9166f3a9ad4cf418328cce7181258d894fb
|
|
BLAKE2b-256 checksum How to use checksums |
4b3ae723b7dd34fbb7c101ac1346a51ec974f0ee9e2a5ca5802bb83f8a700beb
|
| 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 6, 2026.
Transparency logRelease files / wizelit_acp-0.1.22-py3-none-any.whl
| Download URL | wizelit_acp-0.1.22-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24896f77ce575ead245109530d891674ecf6043cd71d8e8f58a9222d9e8c8442
|
|
BLAKE2b-256 checksum How to use checksums |
4db4a500a81fe1d1a82836022265173ebb7820b4c5b2f50b3f35739820abf029
|
| 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 6, 2026.
Transparency log
