Skip to main content

glovebox-monitor

A second model that reads every tool call an agent proposes, before the call runs, and answers allow / ask / deny. This is the supervision layer out of glovebox, packaged on its own so you can run it over your existing isolation instead of adopting glovebox's sandbox.

If pip install glovebox-monitor reports no matching distribution, no release has reached PyPI yet. Install from the repository instead, which tracks the main branch:

pip install "glovebox-monitor @ git+https://github.com/AlexanderMattTurner/agent-glovebox.git#subdirectory=glovebox-monitor"

What is in the box

The package is monitorlib. Every module is stdlib-only apart from the HTTP transport, which uses httpx. httpx is a declared dependency, so pip installs it with the package. When it is missing, every review fails closed with a message that names the fix.

  • A fail-closed design. Every layer that judges a call denies on its own failure. The fail-mode setting structurally refuses allow, an unparsable model reply is a hard deny, and the circuit breaker denies rather than opening the gate.
  • Code-side legs the model cannot be argued out of: a static scan of the proposed command, and a deterministic risk taxonomy that labels the action from its content alone.
  • Memory across calls. The judge sees what the agent already did this trajectory, so a chain assembled one harmless-looking step at a time is visible.
  • Injection hardening. Two independent parsers must agree on the verdict, and untrusted text is stripped of invisible and ANSI bytes before the judge reads it.

Using it with Inspect

Register it as an Inspect approver. It composes with an approver you already have rather than replacing it — the approver contract covers the rules, including the edge where a policy list with no catch-all entry silently rejects every tool it forgot.

What a scaffold-level deployment does not give you

glovebox's own deployment reads the sandbox's network decision log, so it can say what a call actually reached. An approver sees only what the agent proposed. A tool that opens its own connection, and any process the agent started earlier, are outside its view. Pair it with the egress gateway when you need that ground truth.

Metadata

Release files for glovebox-monitor 0.4.11

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for glovebox-monitor 0.4.11
File Size Uploaded Provenance Actions
glovebox_monitor-0.4.11.tar.gz 354.0 kB Without provenance Details for glovebox_monitor-0.4.11.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for glovebox-monitor 0.4.11
File Interpreter ABI Platform Actions
glovebox_monitor-0.4.11-py3-none-any.whl Python 3 none any Details for glovebox_monitor-0.4.11-py3-none-any.whl

Total release size: 752.7 kB

Release files / glovebox_monitor-0.4.11.tar.gz

Download URL glovebox_monitor-0.4.11.tar.gz
Size 354.0 kB
Tags Source
SHA-256 checksum
How to use checksums
5912e77493f9e895bf57cfaeb9a30debfb297fa8b82ee34b0cd2d32fc9970c32
BLAKE2b-256 checksum
How to use checksums
e2f20be78674995a27884e6981c3c80ab7c3bd1740b58482566924106c356a10
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / glovebox_monitor-0.4.11-py3-none-any.whl

Download URL glovebox_monitor-0.4.11-py3-none-any.whl
Size 398.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
82a5cbd4235b74f46bc724f1c5ac24d27c99fc1f2aa7b60360566db0f432554a
BLAKE2b-256 checksum
How to use checksums
ea7549a4de2abc9b1ae9666db2cc2b7a0c8cc6e9061d982dfb9f932a45d5279b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for glovebox-monitor 0.4.11

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page