Connect Jira & a repo
PilotX needs a Jira ticket to read and a repository to work against before it can do anything.
Both connections live under Settings → Integrations (also reachable from the onboarding flow right after you first sign in).
Connect Jira
- Go to Settings → Integrations and open the Jira row's Manage action.
- Enter your Jira site URL (e.g.
https://your-domain.atlassian.net), your Atlassian account email, and an API token. - Jira API tokens are self-service — create one from your Atlassian account settings, then paste it in. PilotX never sees your Jira password.
For the full field-by-field detail, see Jira.
Connect a repository
- From the same Settings → Integrations screen, connect GitHub, GitLab, or Bitbucket — you can connect more than one provider.
- Each provider is authenticated with a scoped access token (a fine-grained personal access token for GitHub, a project or personal access token for GitLab, an App Password for Bitbucket) rather than a full-account OAuth grant, so you can limit exactly what PilotX can touch.
- Grant only what AutoCoder needs to open pull requests: read/write on pull requests and contents, read-only on metadata. PilotX never pushes directly to a branch outside its own proposed PRs.
For provider-specific token scopes, see GitHub, GitLab & Bitbucket.
Watch a repository
Connecting a provider account doesn't automatically hand every repository to PilotX — you choose which repositories to watch from the integrations screen. Only watched repositories show up as targets when triggering a run.
What's next
Once Jira and at least one repository are connected, trigger your first pipeline run — see Your first Run.