Handler
Handler: every agent needs one.
Run coding agents in containers on your Linux machine. Each agent (Claude Code, Codex, Mistral Vibe or pi) runs in its own rootless Podman container that sees only its project folder and reaches only the hosts you allow. A daemon keeps the sessions, which you follow from a web UI, the terminal, your editor (over ACP) or your phone.
Install
You need: Linux with rootless Podman, passt and a systemd user session, and about 3 GB of
disk for the images, built on your machine.
uv tool install handler-ai # or: pipx install handler-ai
handler setup # starts handlerd as a user service, checks this machine, builds the images
handler ui # opens the web UI
The first handler setup downloads and builds the images: from a few minutes to half an hour.
Without uv: curl -fsSL https://github.com/macray/handler-ai/releases/latest/download/install.sh | sh
installs it, then Handler. To update: uv tool upgrade handler-ai.
More
- README: what Handler does, compared with other sandboxes, and a first session.
- Documentation
- Changelog · Issues
1 maintainer
Metadata
1 maintainer
Release files for handler-ai 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| handler_ai-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / handler_ai-0.2.0-py3-none-any.whl
| Download URL | handler_ai-0.2.0-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddbf4265cd96d7f2baff91f6e31534ecd80d960124c3992c08370fc77863029a
|
|
BLAKE2b-256 checksum How to use checksums |
900e52e302af39ad60f08e1046a0591fbfe8f7f9a3360575e18f16876b3364ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 24, 2026.
Transparency logSecurity for handler-ai 0.2.0
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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for handler_ai-0.2.0-py3-none-any.whl
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 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
