GitHub Integration
Vyre's GitHub integration lets Agent create branches, open pull requests, respond to PR review comments, and trigger CI workflows — all without leaving your editor.
Connecting GitHub
Open Integrations Settings
Go to Settings → Integrations → GitHub and click "Connect GitHub."
Authorize with GitHub
You'll be redirected to GitHub's OAuth page. Grant Vyre permission to your repositories. You can grant access to all repos or select specific ones.
Configure default settings
Set your default branch, PR template preference, and whether Agent should auto-assign you as a reviewer on PRs it creates.
Pull requests
Create PRs from Agent
After accepting agent changes on a branch, click 'Open Pull Request' in the review panel. Vyre pre-fills the title, body, and labels.
Link to issues
Reference GitHub issues in your task description. Vyre automatically adds 'Closes #123' to the PR body.
Draft PRs
Use 'Open Draft PR' to share work-in-progress with your team without triggering a full review request.
Auto-label
Vyre analyzes the changes and applies labels automatically: `bug`, `feature`, `refactor`, `docs`, `test`.
Code review
Vyre Agent can participate in code review:
- Review a PR: Ask Agent to review an open PR by linking to it. Agent reads the diff, writes inline comments, and gives a summary verdict.
- Respond to review comments: If a reviewer leaves comments on your PR, Agent can address them. It reads the comments, makes the changes, and pushes a new commit.
- Resolve conversations: After addressing review feedback, Agent can mark conversations as resolved on GitHub.
// Example: respond to review comments
> "Address all unresolved review comments on PR #145.
> For each comment, explain what you changed and why."GitHub Actions
Trigger GitHub Actions workflows from Vyre:
Trigger on PR creation
When Agent opens a PR, GitHub Actions trigger automatically based on your existing workflow files. No additional configuration needed.
Trigger manually
Use the Vyre Command Palette (Cmd+Shift+P → "GitHub: Trigger Workflow") to manually trigger any workflow_dispatch workflow from within the editor.
Read workflow status
Open the GitHub panel in the sidebar to see the status of all CI runs on your current branch. Failed runs show inline annotations on the file and line that caused the failure.
Security
Vyre only requests the GitHub permissions it needs. By default, this is repo scope (read/write to your repositories). We never request access to your organization's settings or billing.
- Tokens are stored in your system keychain, not in Vyre's cloud.
- You can revoke Vyre's GitHub access at any time from github.com → Settings → Applications.
- Enterprise plans can restrict which repositories Vyre can access through GitHub's OAuth app settings.