sbxloop-worker
sbxloop is now Lantern. This project continues as Lantern backend at https://github.com/brettbergin/lantern-backend. This is the final release published to PyPI under this name: Lantern installs from its GitHub Releases, with the
lanternCLI,LANTERN_*environment and~/.lanternhome.
The in-sandbox runtime for sbxloop:
shared host/worker protocol models, the job runner (python -m sbxloop_worker),
and agent backends. Install with the copilot extra inside agent sandboxes:
pip install "sbxloop-worker[copilot]"
You normally never install this directly — the sbxloop host package provisions it into sandboxes automatically.
The claude and codex extras select the other agent backends. codex
installs the Python openai-codex SDK and its matching Codex CLI runtime;
it does not require Node. The worker uses OPENAI_API_KEY and exposes its
own governed local tools plus the host's event/file tool relay. See the
Codex backend design for capabilities and
verification limits.
Metadata
Release files for sbxloop-worker 2.1.36
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sbxloop_worker-2.1.36.tar.gz | 164.4 kB | With provenance | Details for sbxloop_worker-2.1.36.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sbxloop_worker-2.1.36-py3-none-any.whl | Python 3 | none | any | Details for sbxloop_worker-2.1.36-py3-none-any.whl |
Total release size: 294.5 kB
Release files / sbxloop_worker-2.1.36.tar.gz
| Download URL | sbxloop_worker-2.1.36.tar.gz |
|---|---|
| Size | 164.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0493a180876d6b20086245fb1546e6aad371207bdefd8d6230501ece9cce11da
|
|
BLAKE2b-256 checksum How to use checksums |
a6383f1a46f287e63ac6c08f735c6bc9777d976b9c9f5f00accbd10b0ba4b5b9
|
| 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 1, 2026.
Transparency logRelease files / sbxloop_worker-2.1.36-py3-none-any.whl
| Download URL | sbxloop_worker-2.1.36-py3-none-any.whl |
|---|---|
| Size | 130.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18344ee2f760977f52ebaaa54129c5a5e270eb3940eafe6d88f03b0cc0395f4e
|
|
BLAKE2b-256 checksum How to use checksums |
b6b676517f14e5938d2308da63aeb1ebb32baba9f3762b36b658b1dd3120d6b3
|
| 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 1, 2026.
Transparency logSecurity for sbxloop-worker 2.1.36
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
Both files in this release have been uploaded with provenance metadata.
Attestation for sbxloop_worker-2.1.36.tar.gz
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 1, 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.