Quickstart

This guide takes you from zero to your first Pylon-opened pull request. The steps below use GitHub. If you are on GitLab, follow Steps 1-3 and then see the GitLab integration section. You need a Codepylon account, a GitHub account, and at least one repository to connect.

Step 1: Install the GitHub App

Go to your Codepylon dashboard after signing up. Click Connect GitHub. You will be redirected to the GitHub App install flow.

Select the organization or personal account where your repository lives. Choose Only select repositories and pick the repository you want to start with. Click Install.

Codepylon requests only the permissions it needs: read access to code and pull requests, write access to create branches and open PRs, and webhook delivery. See our GitHub App permissions walkthrough for the full list.

Step 2: Connect the repository

After the GitHub App installs, you return to the Codepylon dashboard. Your repository appears in the list. Click Connect next to it.

Pylon begins indexing the repository graph. For a medium-sized repo (50,000-200,000 lines), this takes 2-5 minutes. For a monorepo over 500,000 lines, allow 10-15 minutes for the first index. Subsequent indexes are incremental and complete in seconds.

Step 3: Run your first agent job

Once the repository is indexed, click New job from the repository view. Select an agent type. For a first job, Pylon-Test is a safe choice: it reads your existing test suite and opens a PR adding tests for uncovered code paths, without touching production logic.

Step 4: Review the pull request

Pylon opens a PR on the branch pylon/test-coverage-gap-fill. The PR description lists which code paths were untested, which tests were added, which paths remain uncovered (and the reason each was excluded from the job), and a "Reviewer focus" section that flags the 2-3 generated tests most likely to need human judgment. Review the diff. If a generated test looks wrong, leave a review comment and Pylon will push a corrected commit.

Slack notifications

From the dashboard, go to Settings > Integrations > Slack. Click Connect Slack and authorize the workspace. Choose the channel where PR notifications should go.

Each notification includes: which agent ran, which repository, which ticket was addressed (if linked), the PR link, and whether the CI checks passed.

RBAC and team roles

Available on Team and Enterprise plans. From the dashboard, go to Settings > Team. Roles:

• Admin: full access, including billing and API key management
• Developer: can trigger agent jobs and review job history
• Viewer: read-only access to job history and PR links

Custom agent config per repository

Add a .pylon.yaml file to the root of your repository to override default agent behavior on a per-repo basis. Configuration is validated at job start: an invalid field stops the job with a description of the error rather than running with defaults silently.

agents:
  test:
    exclude_paths:
      - "tests/fixtures/**"
      - "scripts/**"
    min_coverage_gain: 5
  patch:
    auto_trigger_on_cve_severity: high
    notify_slack: true

Configuration options are validated at job start. Invalid config causes the job to stop with an explanation, not a silent failure.

GitLab integration

Available on Team and Enterprise plans. From the dashboard, go to Settings > Integrations > GitLab. You will need a GitLab personal access token with api and write_repository scopes. The flow is otherwise identical to GitHub.

Monorepo scoping

When connecting a monorepo, specify a scope in .pylon.yaml:

scope:
  paths:
    - "services/analytics/**"
    - "services/billing/**"
  exclude_paths:
    - "services/analytics/vendor/**"

Agent jobs will only read and write within the specified paths. They will not traverse into sibling services, even if a module import points there.