AgentQit

Give your coding agent a reusable QA workspace for your application.

Connect the browser, APIs, databases, and events in one place. Define your application's operations once, reuse them across agent sessions, and collect facts that show what happened beyond the UI.

Playwright · HTTP · PostgreSQL · Kafka · S3 · Kubernetes

Works with your existing coding agent through CLI or local MCP. Python 3.12, 3.13, and 3.14; macOS and Linux. MIT licensed.

Why AgentQit

• Load project knowledge on demand. The agent searches your operation catalog and requests the selected operation's parameter schema. Endpoints, reviewed SQL, resource bindings, and usage guides live in your workspace and can be reused across tasks and agents.

• Use credential references in prompts and YAML. The runtime resolves secret values from configured providers, including environment variables and Vault, and applies redaction to structured results.

• Keep one agent connection as the catalog grows. A fixed set of MCP tools discovers and invokes operations by ID. Adding YAML operations adds neither MCP tool definitions nor CLI commands.

• Follow a check across layers. Use a task session to keep browser observations, backend results, IDs, screenshots, and traces together in one evidence journal.

Your team maintains the workspace alongside the application. The agent chooses checks and compares observations with your requirements; AgentQit executes operations and returns facts.

Related MCP server: vouch

Catch a UI/API mismatch

Cancel an order. Verify that both the UI and API show CANCELLED, and show the evidence.

The browser can confirm what the user sees. A declared API operation can inspect the same order. Put both observations in one task session. The agent compares the two states against your requirements and keeps the evidence together.

The included Orders Lab makes this concrete: its --defect-ui mode deliberately keeps showing CREATED after the API has cancelled an order. It runs locally with synthetic data.

Fast track

1. Install and create a workspace

Install uv once, then:

uv tool install --python 3.14 '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. Choose a new directory for workspace init; it creates sample YAML for the next step.

2. Give your agent the setup guide

Use a coding agent with terminal and filesystem access. Copy this task:

Read https://github.com/akimovWare/AgentQit/blob/main/docs/agent-integration.md
and follow the linked workspace and browser guides.

Set up AgentQit for this project in ./my-qa using the installed qa command.
Reuse the initialized workspace. Ask me for the first useful check, expected
behavior, canonical contracts, QA endpoints, my agent host, and credential references.
Configure the workspace YAML and CLI/MCP connection. Validate offline, show the
changes and gaps, and prepare the first check.
Ask for an authorized execution scope before making live calls.

The agent maintains agentqit.yaml, your profile (profile.yaml or qa.yaml), and operations/*.yaml. You supply the application access and expected behavior. Secret values go through the configured provider; share references with the agent. Custom authentication or composition can use a product plugin.

Backend operations work through CLI or MCP. Interactive browser control uses MCP; have the agent configure your host to launch:

agentqit-mcp --workspace /absolute/path/to/my-qa

An execution-only MCP client uses a workspace that has already been configured. The integration guide covers setup and host configuration.

3. Run checks and evolve the workspace

Give the agent a task with requirements:

Verify this checkout change against these requirements. Show the UI/API evidence and any gaps.

Maintain operations through the same agent:

Update the workspace operations from this API contract. Show the changed inputs, effects, YAML diff, and offline validation results.

Keep your application-specific knowledge in the workspace as the application changes. Finish active sessions and restart MCP after updating workspace files. New operations use the same discovery and invocation tools.

What your agent can do

Available after configuring the workspace and access:

Discover operations, inspect schemas, and validate plans offline. Import local OpenAPI contracts into read-only operation drafts for review. Built-in HTTP auth supports Bearer and API-key headers; plugins can supply custom composition.

See CLI and MCP for the fixed toolset and payload benchmark. Actual context use depends on your agent host and the observations requested.

Try the local demo

git clone https://github.com/akimovWare/AgentQit.git
cd AgentQit
uv sync --frozen --extra browser
uv run qa browser install --headless-only
uv run python examples/orders/src/qa_product_orders/demo.py --defect-ui

Open http://127.0.0.1:8765. Point your MCP host at the checkout's .venv/bin/agentqit-mcp with --workspace /absolute/path/to/AgentQit/examples/orders. Follow Orders Lab to authorize the synthetic check, compare UI/API state, and retain the resulting evidence.

Updates and execution boundaries

Update the application with uv tool upgrade agentqit. Finish tasks and stop MCP before upgrading, then restart it; provision browser binaries again if Playwright changed. Workspace YAML and credential configuration remain separate from the installed application. See installation and updates.

Live checks require an authorized scope. Mutations additionally require caller opt-in and environment: qa; MCP also requires an operator-granted host capability. Inspect state before retrying a write with an unknown outcome. Browser contexts provide task isolation; plugins run trusted code. Structured redaction does not sanitize arbitrary screenshots or trace archives. Review artifacts before sharing. See security boundaries.

Guides

One Python distribution, agentqit, provides qa, agentqit-mcp, and the runtime. Browser support is optional; binaries are provisioned explicitly.

MIT · Support · Community guidelines