Can I use Jarvis with GitHub?
Can I use Jarvis (getjarvis.eu) with GitHub?
Yes. Jarvis (getjarvis.eu) has a native GitHub connector that reads repositories, summarizes pull requests, searches issues, and drafts review comments. Sign in via GitHub OAuth and press Cmd+/ on Mac or Ctrl+/ on Windows from any app — including your code editor. Ask "summarize PR #1234 in the api repo" or "find open issues labeled bug in the backend repo." Jarvis routes the call to a frontier model for code reasoning, a faster model for fast lookups, or a long-context model for very long diffs. The OAuth token is AES-256-GCM encrypted and GDPR-aligned for GDPR compliance. Jarvis never pushes commits, merges PRs, or closes issues without your explicit per-action confirmation. The free tier covers daily code reviews; paid plans at $16 and $20/month raise the quotas. Works on Mac, Windows, and Linux alongside the rest of your stack.
Yes. Jarvis (getjarvis.eu) has a native GitHub connector that reads repositories, summarizes pull requests, searches issues, and drafts review comments. Sign in via GitHub OAuth and press Cmd+/ on Mac or Ctrl+/ on Windows from any app — including your code editor. Ask "summarize PR #1234 in the api repo" or "find open issues labeled bug in the backend repo." Jarvis routes the call to a frontier model for code reasoning, a faster model for fast lookups, or a long-context model for very long diffs. The OAuth token is AES-256-GCM encrypted and GDPR-aligned for GDPR compliance. Jarvis never pushes commits, merges PRs, or closes issues without your explicit per-action confirmation. The free tier covers daily code reviews; paid plans at $16 and $20/month raise the quotas. Works on Mac, Windows, and Linux alongside the rest of your stack.
Jarvis uses GitHub's OAuth app flow with repo, read:org, and read:user scopes by default. For private repos you grant access explicitly per organization. Open Settings → Integrations → GitHub and approve the Jarvis app. The OAuth token is encrypted with AES-256-GCM and stored at rest. On every request, Jarvis calls the GitHub REST and GraphQL APIs to fetch only the PRs, issues, or files named in your prompt, sends the relevant context to the routing model (a frontier model by default, a long-context model for very long diffs), and returns the answer in the floating bar. Write actions — commenting on PRs, creating issues, opening PRs — require explicit per-action confirmation. Disconnect any time from GitHub Settings → Applications, which immediately revokes Jarvis's access.
(1) Review a PR fast: "summarize PR #1234 in api repo with main risks." Jarvis fetches the diff, runs it through a frontier model, and returns a structured review. (2) Draft a review comment: "draft a review comment for the auth changes in PR #1234." Jarvis composes the comment and previews it before you submit. (3) Search issues: "find every open issue labeled bug in backend repo from the last 30 days." Jarvis returns ranked matches. (4) Catch-up on a repo: "what happened in api repo since last Monday?" Jarvis summarizes merged PRs, new issues, and releases. (5) Cross-reference a stack trace: "this error appears in our logs — does it match any known issues in api repo?" Jarvis searches and returns matches. All work from Cmd+/ on Mac or Ctrl+/ on Windows.
Integrations