GitHub

Connecting your repo

Open a running session, use the workspace repo panel, and paste a GitHub repo URL or owner/repo plus a fine-grained personal access token with repo access. Meshia encrypts the token, stores the repo connection for that session, and asks the pod agent to clone it into /workspace.

Once connected, the repo appears inside that session workspace and the agent can inspect, edit, commit, push, and open pull requests through the session-scoped connection.

How agents commit

When the agent makes code changes, it commits them to a new branch. Never directly to main. The branch name follows the pattern meshia/<session-name>/<short-description>.

Each commit includes:

• A clear, descriptive commit message
• The agent's identity in the author field (e.g., "Meshia Agent <agent@meshia.io>")
• Only the files that changed. No unrelated modifications

Safety rails

Meshia enforces strict safety rules for all Git operations:

• No force push. Ever. The agent cannot force-push to any branch.
• No merge to main. The agent creates PRs but never merges them. That's your job.
• No destructive operations. No git reset --hard, no git clean -f, no branch deletion on remote.
• No secrets in commits. The agent scans staged files for API keys, credentials, and .env files before committing.

You can't override these rules, even by asking the agent to.

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.