Introduction

PilotX watches a Jira ticket, works out what needs testing, writes test cases, proposes the code changes needed to support them, reviews its own work, runs what it can in an isolated sandbox, and reports back — all before a human has to open an editor.

It runs as one pipeline of seven stages:

Scout → Analyst → TestWriter → AutoCoder → QA Reviewer → Runner → Reporter

Scout reads the ticket and the target repo. Analyst turns that into a testing plan. TestWriter authors the actual test cases. AutoCoder proposes the code changes those tests need — always as a branch/PR, never a direct commit. QA Reviewer checks the proposal before anything runs. Runner executes what's eligible inside an isolated sandbox. Reporter turns the whole run into a readable summary and posts it to Slack.

You control how much of that runs unattended: gate mode decides whether the pipeline pauses for your approval before Runner executes, or runs the whole thing full-auto. See Human gate & approvals.

Where to start

• New to PilotX? Start with Getting started — create an account, connect Jira and a repo, and trigger your first run.
• Want the mental model first? Read Core concepts — what the pipeline actually does, stage by stage, and how the human approval gate works.
• Setting up a specific integration? Jump straight to Integrations — Jira, GitHub/GitLab/Bitbucket, Slack, and Environments each have their own page.
• Something not covered here? Check the FAQ.