Skip to main content
boxd can connect to your GitHub account so your machines can access your private repositories — no SSH keys or personal access tokens to manage. GitHub is one of boxd’s integrations — connect it once and every personal machine can clone and push.

​
Connecting your account

Two ways, both landing the same grant:
  • Console — from the boxd console, click Connect GitHub repos. This redirects you to GitHub to authorize repository access.
  • CLI — boxd integrations connect github from any boxd CLI (laptop, SSH, or inside a machine) prints an authorize URL to approve in a browser.
Once connected, every machine automatically has access to your repos.
GitHub appears in the unified boxd integrations list once connected, so an agent inside a machine sees it alongside Linear and Slack.

​
Using git in your machine

After connecting, git clone and git push work with your private repos out of the box: 
ssh myapp.boxd
git clone https://github.com/you/private-repo.git
cd private-repo
# make changes...
git push
No credentials to enter. boxd injects a git credential helper that handles authentication transparently.
Git SSH URLs (git@github.com:...) are automatically rewritten to HTTPS, so both URL styles work.

​
Disconnecting

From the console, click Disconnect next to your GitHub connection — or run boxd integrations disconnect github from any boxd CLI. Either way revokes the grant at GitHub and clears the token. Future machines won’t have repo access. Existing running machines lose access on their next git operation.

​
What’s authorized

When you connect GitHub repos, boxd requests the repo scope — this grants read/write access to your repositories. Your token is never exposed inside the machine. The credential helper fetches it on demand for git operations only. GitHub CLI (gh) is also pre-installed (and authenticated) on every machine if you prefer using it directly.