Omniscio

Pull Requests

Removed from Omniscio core (the "in-core GitHub detachment") — plugin-only now; this page is kept for historical reference. It used to be a cross-repo GitHub pull-request manager: it listed every PR you were involved in, let you read a PR's description, changed files, checks and review threads, comment, approve, request changes or merge, and open a new PR from a branch. The in-core code is gone — install the GitHub Integration marketplace plugin for GitHub features. See "What it is" below.

On this page

What it is

This page is kept for historical reference: the built-in GitHub feature it describes has been REMOVED from Omniscio core (the "in-core GitHub detachment"). The built-in gh:* GitHub feature — Pull Requests, Issues, Code Search, Releases, and the GitHub notifications channel — has been removed; install the github-integration marketplace plugin for it. GitHub bug-intake, the PR merge-queue, the PR inbox backend, and cloning a GitHub repo when adding a project remain built in.

The removal is complete: the built-in GitHub feature is FULLY REMOVED and plugin-only. The in-core code is gone — there is no longer any way to restore it (the old Settings > Lab > "Built-in GitHub (legacy)" toggle and the AMC_SHOW_INCORE_GITHUB env var no longer exist). It is superseded by the GitHub Integration marketplace plugin, which has full parity plus a codebase browser, a unified siderail, and a repo navigator. Install the plugin for GitHub features.

What the tab did, when it existed: it was a cross-repo GitHub pull-request manager, modeled on GitHub Desktop but focused only on PRs. It listed the pull requests you're involved in across every repo your GitHub account can access, and let you view a PR (description, changed files, checks, review timeline), add a comment, approve or request changes, and merge — all without leaving Omniscio.

It was released for everyone: the Pull Requests entry appeared in the left sidebar by default, with no toggle to find first.

It shells out to the GitHub CLI (gh), so it requires gh to be installed and signed in. If it isn't, the tab shows a Connect GitHub button that walks you through setup (the same one-click install + sign-in flow as GitHub Notifications) and scrolls you to the GitHub settings card.

Where to find it

The surface was a Pull Requests entry in the left sidebar, opening a tab with a PR list down the left and the selected PR's detail on the right. A + button in the tab header opened the create dialog. A Connect GitHub button appeared in place of the list when gh was not set up. The PR-inbox background check was turned on separately in Settings → Lab → "PRs assigned to me in Inbox". With the feature plugin-only, none of this ships in core — the same surfaces are provided by the GitHub Integration marketplace plugin, which you install from the Marketplace.

How it behaves

How to use it

  1. Open it. You clicked Pull Requests in the left sidebar.
  2. Connect GitHub (first run only). If gh wasn't set up, you clicked Connect GitHub — Omniscio installed the CLI if needed and signed you in.
  3. Browse PRs. The left list showed the pull requests you were involved in across all your repos. Filter chips narrowed it to Created by me or Review requested.
  4. Open a PR to see its description, changed files, checks, and the comment/review timeline.
  5. Act on it. You could add a comment, Approve / Request changes, or Merge (with a confirmation step — merge was the one irreversible action).

Creating a pull request

Creating a pull request still ships — in the GitHub Integration plugin, and this section describes only the removed built-in version of it. With the plugin installed, a repository's pull-request list has a New pull request button that opens the create form; the flow, its branches and template prefill, the draft option and the CLI endpoint are described in integrations-github.md. The steps below name the retired entry point (a + in the tab header) and the retired gh permission grant, neither of which the plugin has.

When GitHub was connected, a + button appeared in the Pull Requests tab header. It opened a dialog that created the pull request on GitHub directly, with no local checkout involved.

  1. Pick the repository. The dropdown listed the repos from your PR list plus your own repos; choosing Type a repository... let you enter any owner/repo you could access.
  2. Pick base and head branches. Both lists came from the repo's real branches on GitHub (the first 100 alphabetically, with the default branch always included; a note told you when the list was truncated). There was no free-text branch field, so the dialog could never invent or push a branch.
  3. Title and description. If the repo had a pull request template, its first template prefilled the description; once you had typed in the box, switching repos never overwrote your edits.
  4. Optionally tick "Open as draft", then click Create pull request (or press Ctrl+Enter).

If the head branch already had an open pull request into the chosen base, the dialog showed it and disabled Create for that pair; picking a different base was still allowed. Creating needed the GitHub repo permission (the same one approve / request-changes / merge used); if your gh login did not have it, Omniscio ran the one-click grant first. On success the dialog showed the new PR number with a View on GitHub button; it could take GitHub a minute to show the new pull request in your list. Any failure was reported in plain language inside the dialog.

Review comments on specific lines

Beyond the top-level comment box, you could hold a real line-level review conversation right inside the diff, so you rarely needed to open github.com to review.

  1. Open the changed file. In Changed files, you expanded a file. A small comment-count badge on each file row told you which files already had review conversations.
  2. Read the threads. Existing review threads appeared inline, directly under the line they were left on, showing every reply and whether the thread was resolved. Threads whose line was no longer in the current diff were grouped under an Outdated heading at the top of the file so nothing was lost.
  3. Reply to any thread from the box at the bottom of it.
  4. Start a new comment on a line. Hovering a diff line and clicking the + that appeared let you type a note and send it.
  5. Resolve or reopen a thread with its toggle once it was handled.

Posting any of these needed the GitHub repo permission (the same one approve / request-changes / merge used); if your gh login did not have it, Omniscio ran the one-click grant first.

PRs assigned to me

This setting is the one live piece of the surface. Turn it on in Settings → Lab → "PRs assigned to me in Inbox" (it requires gh signed in) and Omniscio checks GitHub in the background every few minutes for the two kinds of pull request waiting on you:

  • Review requested — someone asked for your review.
  • Changes requested — one of your own PRs got changes requested and is back in your court.

What that background check does today is cache the matching PRs (in pr_inbox_snapshots). It no longer renders any of them: the pr-inbox source has been retired from the renderer's inbox source list, so the unified Inbox draws no row for it even with the switch on, and there is no Pull Requests tab for a row to open. The cached rows stay reachable for agents over the CLI (GET /pr-inbox), and Omni, the AI Project Manager, is told about that read so it can answer "what pull requests are waiting on me?" with its own key. It is off by default, so there are no background GitHub calls, and no rows to read, until you enable it.

The automated merge queue is a separate feature from this manual PR manager and is described in pr-merge-queue.md — the two are frequently confused, so start there if you want queueing rather than reviewing. If you need the marketplace plugin that now carries all the GitHub surfaces this page used to provide, see plugin-marketplace.md. The sibling GitHub features that were removed in the same detachment have their own pages in github-issues.md, github-code-search.md and github-releases.md. For how the Inbox handles an integration, read inbox-overview.md, and for the git safety rules that govern anything landing on a shared branch, git-guardrails.md.

Last verified 2026-11-06