AgentQit
Application testing tools for AI agents.
AgentQit exposes typed browser actions, reviewed backend operations, and observations with evidence. The agent selects checks from requirements and compares the returned facts with expected behavior. CLI and local stdio MCP share one execution runtime.
CPython 3.12, 3.13, and 3.14; macOS and Linux.
Install
With uv installed:
uv tool install --python 3.12 'agentqit[browser]>=0.1,<0.2'
qa browser install --headless-only
qa workspace init --directory ./my-qa --name sample
For backend-only use, omit [browser] and browser provisioning. Pin a reviewed
version such as ==0.1.0 for a reproducible installation.
Configure the workspace with reviewed operation YAML, your QA endpoints, and explicit credential references. Ordinary integrations use YAML; reusable catalogs and custom composition can use plugins.
Connect an agent
Configure your MCP host to launch:
agentqit-mcp --workspace /absolute/path/to/my-qa
Interactive browser sessions use MCP. CLI also supports backend execution,
discovery, planning, and diagnostics. Writes require operator authorization,
caller opt-in, and environment: qa. Browser actions use scoped references;
evidence artifacts remain local and private by default.
Update
uv tool upgrade agentqit
Updates follow the source and version constraints used at installation. Finish tasks and stop MCP before upgrading, then restart it. Re-provision browser binaries when Playwright changes. User YAML and credentials are separate from the application.
Guides
- Project overview
- Workspace and authentication setup
- Agent integration
- Browser sessions and evidence
- Installation and updates
- Compatibility
- Security boundaries
A completed operation is an execution fact. Business conclusions belong to the caller. Unknown write outcomes require state inspection before retrying. Plugins execute trusted code; this runtime is a local tool, not a shared remote service.
1 maintainer
Metadata
1 maintainer
Release files for agentqit 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 | Provenance | Actions |
|---|---|---|---|---|
| agentqit-0.1.0.tar.gz | 346.9 kB | With provenance | Details for agentqit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentqit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agentqit-0.1.0-py3-none-any.whl |
Total release size: 506.9 kB
Release files / agentqit-0.1.0.tar.gz
| Download URL | agentqit-0.1.0.tar.gz |
|---|---|
| Size | 346.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ace494717406566fe329e6be63ec3afbf026621d35ef05a2d30d6d908b303926
|
|
BLAKE2b-256 checksum How to use checksums |
9fcdd342455cb08dfda5194ebf85d326731747b9a9a2e29fb5f20a3eb0fc5f2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / agentqit-0.1.0-py3-none-any.whl
| Download URL | agentqit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 160.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98f36a0773caf6d9c48f3bb0ac1e13d59cdfa1154dcc2ec095f0bd43e9c4618d
|
|
BLAKE2b-256 checksum How to use checksums |
7dc84a29f490ca1a5699bc5dca64cfc14ebe7bc128934ddc5fb6af429a54c8c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for agentqit 0.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agentqit-0.1.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 Nov 2, 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.
