One Coordinator
The Coordinator turns the mission into bounded work, receives reports, and chooses the next safe action.
Workforce / collaboration
A QA team that talks through the work, not around it.
Matrix QA makes worker dialogue visible in the Run Console: assignments, proposals, approvals, handoffs, evidence, and completion states remain durable and redacted.
matrixqa / run-001
$ matrixqa inspect --target authorized-url
[01] browser session initialized
[02] journey instructions loaded
[03] evidence capture active
✓ For teams that want parallel investigative thinking without giving autonomous workers an ungoverned path to act.
report → screenshots · console · network · timestamps
Specialized workers
Discovery, core-flow, responsive, interaction, and reproduction/evidence responsibilities can be separated by worker role.
Conversation in the console
Named agents can report progress, ask for a handoff, propose a check, and return evidence-linked findings.
Capacity-aware execution
Leases and capacity snapshots prevent the team from treating logical workers as unlimited physical browsers.
The workflow
From one URL to evidence you can act on.
- 01
Coordinator assigns a lease
The worker receives a defined scope, allowed actions, target origin, and deadline.
- 02
Worker reports and proposes
The worker can describe progress or suggest the next check without bypassing approval policy.
- 03
Coordinator closes the loop
The console records the response, evidence references, completion state, and any safe handoff.
How a real exchange should read
A useful collaboration transcript is specific: “SK3-sub-agent is checking the mobile-like viewport; the navigation wraps at the breakpoint. Should SK4 verify keyboard focus on the same menu?” The Coordinator can approve, redirect, or close that proposal based on coverage and capacity.
The goal is observable work, not theatrical chat. Messages remain tied to durable workforce state and the authenticated Run Console boundary.
Five logical slots are not five guaranteed sessions
The launch contract exposes five logical worker slots for Starter collaboration. Actual browser processes, queue capacity, deployment limits, and run policy can constrain simultaneous execution. This distinction keeps the product promise useful without hiding infrastructure limits.
For the underlying usage model, read Matrix Unit metering and for the broader run mode read Standard Adaptive testing.
Safety is part of collaboration
Worker messages are bounded and redacted before they reach customer-facing console views. The workforce records coverage claims, conflict signals, proposals, approvals, and leases so no worker can silently create arbitrary work or leave the approved target scope.
Start with a focused Quick Smoke journey when you are validating a new target.
Explore the QA library
View all capabilitiesFind the testing guide that matches your next question.
Questions teams ask
Do the workers chat with each other?
The Run Console can show durable named-agent messages, handoffs, proposals, approvals, and responses. The Coordinator remains the governing decision point.
Can a worker take any action it wants?
No. Worker proposals require safe task leases and Coordinator or scheduler approval within the run’s scope and policy.
Is this feature included in Free?
Free includes one logical worker. Starter is the launch tier for governed five-worker collaboration.
Turn your next deploy into a proof, not a guess.
Start with one authorized URL. Matrix QA walks the journey and returns the evidence your team needs to decide what ships.