Skip to content
AFK / Docs

Search page titles and summaries. Shortcut: Ctrl / ⌘ K.

38 pages found

ProductPricingCommunity
Start free

GitHub App integration

AFK can connect GitHub App installations so browser-spawned remote Docker sessions and saved automations can browse private repositories and clone them with short-lived installation tokens.

Why use the GitHub App?

You can still paste a repository URL when launching a Docker-backed session. The GitHub App path is safer and easier for teams: AFK lists the repositories the installation can access and exchanges the installation for a short-lived clone token at session start, avoiding long-lived personal access tokens in spawn forms or webhook definitions.

Connect an installation

  1. Open Account → Git in the AFK browser UI.
  2. Start the GitHub App install flow and choose the user or organisation repositories AFK should be allowed to access.
  3. Return to AFK. The account page shows the connected installation and repository access state.

Use it from the spawn modal

  1. Click New session.
  2. Choose a Docker-backed remote repository session.
  3. Select a connected GitHub installation and repository from the picker.
  4. Pick daemon, connection/model, permission mode, resources, and the task prompt, then spawn the session.

The daemon receives the remote repository configuration, requests a short-lived clone token through the Hub, clones in Docker, and starts the agent in the container. Host worktree settings do not apply to Docker sessions because Docker already provides filesystem/process isolation.

Use it from automations

Saved webhook and schedule automations can also target repositories from a connected GitHub App installation. This is useful for CI failure triage, release preparation, dependency audits, and other workflows that should start a remote Docker session without manual repository entry.

Troubleshooting

  • If no repositories appear, confirm the GitHub App installation has access to the repository and reconnect if access was changed in GitHub.
  • If a clone fails, check that the selected daemon can run Docker and has network access to GitHub.
  • If an org repository is missing, switch to the correct AFK org context before opening Account → Git or the spawn modal.