Skip to main content

jharness-tools

Ready-to-use filesystem, shell, interaction, and child-agent tools implementing the JHarness kernel tool contracts.

uv add jharness-tools
from jharness.tools import GlobTool, GrepTool, LsTool, ReadTool

Filesystem tools are rooted in one workspace and reject path escapes. BashTool uses a bounded non-interactive Bash process and a minimal environment by default, but it is not an operating-system sandbox: commands retain the filesystem and network access granted by the host. inherit_environment=True explicitly exposes the full host environment.

Workspace path checks are not a mount namespace; mutually untrusted writers need dedicated filesystem isolation and hard-link controls. Process-tree cleanup is best effort, so containers—especially PID 1—must forward signals and reap child processes.

Interaction tools suspend for a host response. Child-agent tools accept the narrow AgentBackend protocol. For a single-process host, InMemoryAgentBackend provides concurrent supervision, parent-run authorization, idempotent creation, waiting, and cancellation:

from jharness.kernel import Runtime
from jharness.tools.agent import InMemoryAgentBackend

child_runtime = Runtime(model=model, tools=child_tool_catalog)
agent_backend = InMemoryAgentBackend(
    child_runtime,
    system_prompt="Follow the delegated task and return a concise result.",
)

Pass agent_backend to AgentTool, AgentGetTool, AgentWaitTool, and AgentCancelTool. After a parent suspension, the host can await the in-memory implementation's wait_for_terminal(agent_id, requester=parent_context) and deliver the snapshot with resume_agent; other backend implementations may use their own durable notification mechanism. The in-memory backend retains idempotency records for its lifetime, stores them only in its process, and must be used from one asyncio event loop. Hosts requiring bounded retention, crash recovery, or shared workers should implement AgentBackend with durable storage. The host remains responsible for choosing trusted child Runtime configuration and recording telemetry.

Installing this distribution installs the exact matching jharness-kernel version.

Metadata

Release files for jharness-tools 0.9.0

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

Source distribution (sdist)

Source distribution for jharness-tools 0.9.0
File Size Uploaded Provenance Actions
jharness_tools-0.9.0.tar.gz 57.2 kB With provenance Details for jharness_tools-0.9.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for jharness-tools 0.9.0
File Interpreter ABI Platform Actions
jharness_tools-0.9.0-py3-none-any.whl Python 3 none any Details for jharness_tools-0.9.0-py3-none-any.whl

Total release size: 133.7 kB

Release files / jharness_tools-0.9.0.tar.gz

Download URL jharness_tools-0.9.0.tar.gz
Size 57.2 kB
Tags Source
SHA-256 checksum
How to use checksums
daa3619af3cbe3a6ae9f39f7bc896bfbab6ab3a8b27140d1d58bfa4ced5be1eb
BLAKE2b-256 checksum
How to use checksums
95a1baee7f9557de777dfcd0e68ca2fabfc3b6cb1495fc01fe2433ff1beddd5f
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 Aug 30, 2026.

Transparency log

Release files / jharness_tools-0.9.0-py3-none-any.whl

Download URL jharness_tools-0.9.0-py3-none-any.whl
Size 76.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cd064a6a15029224b1cf5a620724b56e45cb0aa239ee703f5217a44f46397060
BLAKE2b-256 checksum
How to use checksums
ed57ea130dc881afc880fd4618b67afe4c9c0af38e40bd7644a51002111d88d7
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 Aug 30, 2026.

Transparency log

Security for jharness-tools 0.9.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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for jharness_tools-0.9.0.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 Aug 30, 2026.

Transparency log

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