MeshiaDocs
All docsPricing
Continue
All docs
Getting started
Your first sessionThe workspaceSSH access
Core concepts
Agent rolesSoon
ExperimentsResearch plans
CanvasSoon
WorkflowsSoon
Integrations
External AI agents (MCP)Connect MeshiaGitHub
WebhooksSoon
Notifications
Platform
Billing and plansAgent memoryMulti-chatKeyboard shortcuts
Reference
GPU catalogAgent toolsSecurityLimits and quotas
Integrations

GitHub

Connect GitHub

Ask the agent to connect GitHub in your workspace chat. The connection card gives you a code and a GitHub approval link. Approve access on GitHub, then return to chat. You can connect before compute is attached.

Account connections are saved once and available across your personal workspaces. Team and workspace connections follow their own access scope. You can add multiple GitHub accounts and choose which account the agent uses.

Clone a repository

Tell the agent which repository to clone, using a GitHub URL or owner/repo. Once workspace compute is ready, the agent clones it into /workspace/repos/. You do not need to select a repository in a workspace picker.

Private repository access follows the selected account's permissions. Credentials stay in Meshia's encrypted storage; the clone uses a credential broker.

Git works normally in the workspace. git clone, fetch, pull and push to any github.com remote (HTTPS or SSH form) use your connected GitHub account on every kind of compute. There is nothing to set up: Meshia keeps your connected accounts and makes them available to the workspace's tools, outside your files so they are never saved or synced. If GitHub isn't connected, Git says so and the agent asks you to connect it.

How agents commit and push

The agent commits and pushes only when you ask, and uses the branch, message and authorship you ask for. It never force-pushes unless you ask. What a push may change is decided by your account's GitHub permissions and the repository's branch protection rules.

PR workflow

When the agent's work is ready for review, it opens a pull request. The PR includes:

  • A summary of what changed and why
  • Test results if applicable
  • A link back to the Meshia session for context

You review and merge the PR through GitHub as normal. The agent can respond to PR review comments if you @mention it.

Branch management

The agent creates a branch per logical unit of work. If you ask it to do three unrelated tasks, it creates three branches and three PRs. This keeps diffs small and reviewable.

← Connect Meshia