Pythe

GitHub and GitLab

Connect GitHub so an Engineer can clone private repos, branch, run tests and open issues and pull requests, each after your approval. GitLab is read-only.

Updated 2026-10-13

Connect GitHub

  1. Press Connect. GitHub opens its authorisation page.
  2. Review the account at the top, and press Authorize.
  3. If your code lives in an organisation, press Grant next to that org before authorising.

Pythe reads repository metadata: repos, stars, visibility and recent activity. You can also give a public repo address during onboarding so Pythe reads it for context.

What an Engineer does with a repo

github_repo_edit works on a real repository from the agent’s computer.

  1. Clone it. Private repos need your GitHub connection; public ones work without.
  2. Create a branch (default pythe/<short-summary>), from the base branch you name or the repo’s default.
  3. Write or edit files, then run commands in the repo: install, tests, formatters.
  4. Commit.
  5. If a pull request was asked for, push the branch and open it. That step goes to you for approval.
  • The engineer’s playbook says to test before opening a PR and report only what it ran.
  • Paths can’t climb out of the repo and .git is off limits.
  • Direct git push and gh writes from the shell are refused. See Guardrails.

Issues and pull requests

github_open_issue and github_open_pr are approval-gated actions that autopilot can skip on Premium. The pull request card shows the title, body and branch.

GitLab

GitLab.com is read-only: projects, visibility, stars, recent activity and group membership. Self-managed GitLab instances are not supported yet.

Related

·