This release is a pre-release and may not be stable for production use.
bazaar-contrib-harness
Enable the harness provider registry. Install a concrete harness provider separately.
Call a registered builder's inspect(workspace, timeout=...) to query availability,
the provider CLI version, models, reasoning efforts, workspace skills and MCP servers before
creating an agent or session. The result is a HarnessInspection; its error
field reports query failures alongside any metadata already returned.
HarnessInspection.mcp_servers contains HarnessMcpServer entries with the server
name, provider-reported authentication status and discovered HarnessMcpTool entries.
Each tool carries its name, optional description and actual JSON input schema.
Providers query their MCP inventory in the requested workspace and preserve partial
results in the inspection if a later query fails.
SessionInput.approval_policy uses ApprovalPolicy.ON_REQUEST or NEVER.
sandbox_policy uses SandboxPolicy.WORKSPACE_WRITE or DANGER_FULL_ACCESS;
network_access carries the selected network permission. The upstream agent
selects these policies from the session's Actor. Each provider translates them
into its native protocol and retains them when resuming that session.
Provider configuration reads the fields it uses and ignores additional fields.
Execution calls return confirmed or failed. A failed call or terminal output
carries HarnessFailure with a provider-neutral reason, the actual message
and an optional original error code. needs_reconciliation asks the agent to
query and reconnect to the existing execution before deciding its final result.
Recovery and retry errors go to audit/logs; Channel feedback shows the final
failure if no execution provider completes the request.
An approval request offers allowed_scopes using ApprovalScope, a StrEnum
with ONCE, SESSION, and ALWAYS. ApprovalResult.scope selects one of those
scopes and defaults to ONCE. The decision remains approved or rejected.
Providers map the selected scope into their own authorization protocol.
In dangerous_individual mode, the agent approves every request directly.
bcn contrib add harness --enable
The corresponding entry in config.toml:
version = "5"
[[contribs]]
package = "bazaar-contrib-harness~=0.3.0rc1"
[[contribs.enabled]]
entry = "harness-builders"
1 maintainer
Metadata
1 maintainer
Release files for bazaar-contrib-harness 0.3.0rc4
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 |
|---|---|---|---|---|
| bazaar_contrib_harness-0.3.0rc4.tar.gz | 10.1 kB | Without provenance | Details for bazaar_contrib_harness-0.3.0rc4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bazaar_contrib_harness-0.3.0rc4-py3-none-any.whl | Python 3 | none | any | Details for bazaar_contrib_harness-0.3.0rc4-py3-none-any.whl |
Total release size: 22.8 kB
Release files / bazaar_contrib_harness-0.3.0rc4.tar.gz
| Download URL | bazaar_contrib_harness-0.3.0rc4.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
929279ba046f8a8ec1070b4dc25b330eaf7ebb4df238007125f5aaf5b7ffdd16
|
|
BLAKE2b-256 checksum How to use checksums |
6996e1100df12545610bbef530c3c44cc158578eda61100d98f31a7090ab8288
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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 / bazaar_contrib_harness-0.3.0rc4-py3-none-any.whl
| Download URL | bazaar_contrib_harness-0.3.0rc4-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a16dcbac7b133fb25221cd2bd2b975c82b211839b0dc8f7ae520a1a5e168037
|
|
BLAKE2b-256 checksum How to use checksums |
6950d8de9d6ed41f581da23842acc13377fb7b30aa1f450b2ee20c90da5d6651
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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 bazaar-contrib-harness 0.3.0rc4
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.
