Your coding agents

GitHub

See your pull requests and issues across every repository, then hand any of them to a coding agent to review, fix its checks or solve it.

FreeMacCoding agentGitHub CLI

Choose an example to copy it, then try it in Jevie.

Use itHow it worksLimitsWhere it's kept

Use it

See them

• my pull requestspull requestsYours and others' in your repositories, those waiting on you first
• prs waiting on my reviewreview requestsOnly the ones someone asked you to review
• pull requests in my-appOne repository, by its project folder or owner/repo
• github issuesOpen issues in your repositories and those assigned to you

Hand them to an agent

• review pull request owner/repo#12review itA coding session reads the diff and tells you its findings
• fix the checks on owner/repo#12A session reads the failing logs, fixes them and commits
• address the comments on owner/repo#12address the review comments on PR 12A session works through each open review thread (file and line, and what was said), changes the code and commits; Address comments is on a row whose review asks for changes
• solve issue owner/repo#7solve issue #7A session on a new branch, given the issue and its comments

How it works

Each row shows the title, who opened it, whether its checks pass, its review state, and which session is working on it. A step starts a coding-agent session on the session wall that knows which pull request or issue it is about; fixes and addressed comments happen in a separate checkout on the pull request's branch, so your own files are never touched. Only open review threads are handed over: resolved ones and those on lines that have since changed are left out, and with none open Jevie says so and starts nothing.

Reviewers' words go to the session as text to consider, never as instructions.

Jevie reads GitHub through the gh command you are already signed into. It never comments, reviews, pushes or merges on its own: each session asks you first.

Limits

• Needs gh installed and signed in.
• issues alone means the page's or your tracker's; say github issues or name the project.
• Checks are read when the view opens, not updated live.
• A pull request with a very long review is cut short: up to 500 threads, each with its first page of comments and three more, and the session is told there is more.

Where it's kept

In Jevie, help github answers from this page as you type.

Related

Updated 27 October 2026 · Something wrong or missing? Tell us