blemees-container
Run blemees-agentd inside
a sandboxed container with full participation in the existing operator
(blemees-tui) and peer-mesh
(blemees-peer) channels.
A session running inside a container is indistinguishable from one running on the host — to the TUI, to the peer mesh, and to other agents addressing it.
Status — v0.1.0 (pre-alpha): Package scaffold only. The CLI shell is in place; the engine drivers and lifecycle logic land in subsequent releases. See
docs/IMPLEMENTATION_PLAN.mdfor the phase-by-phase roadmap.
Install
pip install blemees-container
Once shipped to Homebrew:
brew install blemees/tap/blemees-container
What it does
blemees-container composes the right docker / podman / nerdctl
invocation to spawn a containerized agentd, wires up the bind-mounts
and env so the contained agent appears on the host's peer mesh, and
manages session state copy-in/copy-out so sessions are portable
between host and container.
It is not a daemon. It's a CLI that delegates container lifecycle to the host's container runtime.
blemees-container start <name> --image <image> [options]
blemees-container stop <name> [--force]
blemees-container list
blemees-container exec <name> [--] <cmd> [args...]
blemees-container logs <name> [--follow]
blemees-container rm <name>
How it fits
┌────────────────┐
│ TUI │
└────────┬───────┘
│ blemees-agent/1
┌───────────────────────┼─────────────────────────────┐
│ │ │
▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ agentd │ │ agentd │ │ agentd │
│ (host) │ │ (container) │ │ (container) │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ │ │
└───────────────┬───────┴─────────────────────────────┘
▼
┌──────────────┐
│ peerd │
└──────────────┘
The TUI connects to every agentd it finds (host plus every
container) and merges their session lists into one view. Identity
propagation via BLEMEES_AGENT_HOME makes a session in
/workspace/foo (bind-mounted from ~/projects/foo) addressable on
the peer mesh as home:~/projects/foo#…, exactly as if it were
running on the host.
Documentation
docs/SPEC.md— full v0.1 design (1280 lines).docs/IMPLEMENTATION_PLAN.md— phase breakdown of the 12 implementation steps with parallelization and risk hotspots.
License
MIT — see LICENSE.
Metadata
Release files for blemees-container 0.1.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 | |
|---|---|---|---|
| blemees_container-0.1.0.tar.gz | 30.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blemees_container-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 kB
Release files / blemees_container-0.1.0.tar.gz
| Download URL | blemees_container-0.1.0.tar.gz |
|---|---|
| Size | 30.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1a068966578c2d89ce62649be6a2b9a3d22ca9dacaf8e8ca8b464f58a5b823f
|
|
BLAKE2b-256 checksum How to use checksums |
3b1acfd711ca5739f8c640b332fb09371e8ba3a3a79c3b1521eaffd04d166a12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 6, 2026.
Transparency logRelease files / blemees_container-0.1.0-py3-none-any.whl
| Download URL | blemees_container-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b8bd791d0e0befdf60fe94244cb24cff8925cd1fdc3cf4779781e92ae532fea
|
|
BLAKE2b-256 checksum How to use checksums |
d33c602c54e699ee04bddba59351eaf9ed355f843faf6fa65596e350b52bf2f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 6, 2026.
Transparency log