orchestra Issues & pull requests
Read and triage repository context, then start an agent session without leaving Orchestra.
On this page
Connect a GitHub repositoryBrowse issues and PRsRead the detailsEdit status, assignees, and labelsWork on an issue, review a PRConnect a GitHub repository
Install GitHub CLI and sign in using the command below. Add a project whose Git repository has a GitHub remote. Issues & PRs appears first beneath it in the sidebar.
Orchestra prefers the origin remote. If it is not on GitHub, the other remotes are checked. Requests use your existing gh login for public and private repositories.
gh auth loginBrowse issues and PRs
Switch between the Issues and Pull requests tabs. Filter by status, search by title or number, and refresh the list. To refresh automatically while the page is visible, choose an interval in Settings → General → GitHub Auto Refresh.
Each row shows the title with its author inline, labels, assignees, status, and update time. Open an item to read it inside the app. Returning to the list preserves your filters.
Read the details
The detail heading shows the title, author, and update time. The item number in the toolbar opens it on GitHub, and ⌘[ returns to the list. Descriptions and comments render in the selected app theme. Pull requests also show their branches and a summary of changes.
Edit status, assignees, and labels
Change an item’s metadata from the detail view. Changes are saved to GitHub and update in place.
- Status: reopen, or close an issue as completed, not planned, or a duplicate. Pull requests can be closed or reopened; merged pull requests cannot.
- Assignees: toggle people on or off.
- Labels: search, select, and save.
Work on an issue, review a PR
Click Work on in an issue, or Review in a pull request. Orchestra starts a session with the Default Agent in a new worktree, names it #<number> <title>, and supplies the item’s URL as the first prompt.
To use a different agent, model or effort for this item, open the arrow beside the button and choose them before starting. Orchestra lists the models each agent reports: Claude Code, Codex, Pi, OpenCode, Grok Build and Antigravity CLI offer a model, and Claude Code, Codex and Pi also offer an effort. Default keeps the agent’s own setting. Your choice is passed to the CLI each time the session starts, including when you resume it; Orchestra does not change the agent’s configuration files.
When sessions were started for an item, a terminal button appears on its row and beside Work on or Review. Hover over it to see the sessions, and click it to open the most recent one.
Grok Build does not accept an initial prompt, so its session starts without one.