How we handle GDPR data-subject requests on a deadline
Legal
The QA agent we run on Kortix — connected to GitHub and our test environment. It checks out each PR, runs the suite, exercises the change, and posts the result.

Code review catches problems a person can find by reading a diff. It misses the ones you only find by running the change: a test that passes locally but flakes in CI, a path that works in the happy case and 500s on an edge case, a migration that reads fine but locks a table under load. These tend to surface in staging or production, after the PR is approved.
We run a QA agent on Kortix that does this checking when the PR opens. This is how we QA our own changes, including the connections and guardrails involved.
Some bugs don't show up in a diff. A reviewer reads the code and approves, but no one has checked out the branch, run the suite, hit the new endpoint, and watched what happens. CI runs the tests the author wrote; it doesn't cover the paths they missed.
The common fixes are incomplete. Green CI shows the existing tests pass, not that the change is correct. A manual QA pass is thorough but slow and lands after the review. A generic AI reviewer only sees the diff; it can't run the branch, so it misses failures that only appear at runtime.
On Kortix, each PR triggers an agent. On open and on every push, the PR spawns an isolated session (a cloud sandbox) with scoped access to the branch, the test suite, a deployable test environment, and the Cloudflare edge in front of it. The agent checks out the change, runs the suite, exercises the new behavior on a live deploy, and posts a pass/fail result on the PR.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the pr-qa skill and the 5-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a PR QA agent in this workspace.
Create the agent agents/qa-agent.md. Its job is to QA every new pull request revision on owner/repo against the test environment and post a pass or fail result. It uses the gh CLI with the GH_TOKEN secret, and deploys with the TEST_ENV_DEPLOY_TOKEN secret.
Create the skill skills/pr-qa/SKILL.md with these rules:
Add a cron trigger pr-qa-sweep to kortix.yaml. It runs the qa-agent agent every 5 minutes with the prompt "Load the pr-qa skill and QA every PR on owner/repo whose current head has no QA result yet."
Tell me which of these connectors are not connected yet. Tell me if the GH_TOKEN or TEST_ENV_DEPLOY_TOKEN secret is missing.
Open a change request with all of it. Do not merge it.
Add a GitHub token as the GH_TOKEN secret and your test-environment deploy
token as TEST_ENV_DEPLOY_TOKEN. Both are injected at runtime and scoped to
this agent. The edge check is a public HTTPS request and needs no credential.
Checks out each new PR and posts a pass or fail result.
Deploys each PR branch to the test environment.
Serves the edge the agent re-checks each change through.
Merge the change request, then start a session with the qa-agent agent and send this prompt. Replace owner/repo with your repository. Read the first results on the PRs before you let the schedule take over.
QA the open PRs on owner/repo.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 5 minutes, each run on its own cloud computer. It QAs only the PR
revisions that have no result yet. To change the time, edit the cron line, or
open Triggers in the workspace.
triggers:- slug: pr-qa-sweep name: PR QA sweep on: cron: "0 */5 * * * *" run: agent: qa-agent prompt: Load the pr-qa skill and QA every PR on owner/repo whose current head has no QA result yet.The agent has no production credential. It deploys only to the test environment, tears each deploy down, and never merges. Its output is a check and a comment on the PR. A person reads the result and merges.
Each PR revision gets one check and one comment. This is what a sweep looks like in the session:
QA'd 2 new PR revisions. 1 passed: 412 tests green, and the new endpoint returned 200 direct and through the edge. 1 failed: a redirect works direct to the origin but returns 404 through the edge. Its comment has the failing request and the repro steps.
Once it works, paste any of these into the same session.
When a run finds a new edge case, add it to memory/qa-known-issues.md with the PR link, and open a change request for that file only.
For each PR that changes a page, add a screenshot of that page on the test deploy to the PR comment.
Every day at 17:00, post to #eng a list of the PRs that failed QA that day, with the failing command for each one.
The agent has access to the test environment and the edge, so the access is scoped and contained:
Runtime failures that a diff can't show now surface on the PR when it opens, with the failing command, the logs, and the repro attached. Reviewers spend their time on design rather than checking out branches by hand, and the changes that reach staging have already been run against the test environment.