Git Integration

A complete guide to connecting Git providers and using repositories with AgentsMesh.

Overview

AgentsMesh integrates with popular Git hosting platforms to provide seamless repository access for AI agents. This guide covers the end-to-end setup process.

GitHub (OAuth)

Connect your GitHub account using OAuth for one-click authorization:

Go to Settings → Personal → Git Settings
Click Connect GitHub
Authorize AgentsMesh in the GitHub popup
Select which repositories to grant access to
Your repositories will appear in Settings → Repositories

GitLab (Personal Access Token)

Connect GitLab using a Personal Access Token:

In GitLab, go to Settings → Access Tokens
Create a new token with api and read_repository scopes
In AgentsMesh, go to Settings → Personal → Git Settings
Click Add GitLab Provider and paste your token
Enter your GitLab instance URL (for self-hosted)

Self-Hosted GitLab: Enter the full URL of your GitLab instance (e.g., https://gitlab.yourcompany.com).

Gitee (Personal Access Token)

Connect Gitee using a Personal Access Token:

In Gitee, go to Settings → Personal Access Tokens
Create a new token with projects scope
In AgentsMesh, go to Settings → Personal → Git Settings
Click Add Gitee Provider and paste your token

SSH Key Management

For repositories accessed via SSH, ensure your Runner has the correct SSH keys configured:

Generate an SSH key pair on your Runner machine
Add the public key to your Git provider (GitHub/GitLab/Gitee)
The Runner will use the SSH key when cloning repositories

Docker Runners: Mount your SSH keys as a read-only volume: -v ~/.ssh:/root/.ssh:ro

Using Repositories in Pods

Once a repository is connected, you can link it to Pods:

When creating a new Pod, select a repository from the dropdown
The Runner clones the repo and creates an isolated Git worktree
The AI agent starts in the repository's working directory
All changes are isolated to the Pod's worktree