Pattern Oracle (Plugin)
Pattern Oracle is a built-in Omniscio plugin, off until you switch it on, that reads your GitHub pull requests over a rolling window and writes a periodic report of the recurring patterns it found, ranked, with recommendations you can track. It reads pull requests only, because its session analysis cannot reach the local session list today.
On this page
Built-in plugin — Pattern Oracle ships inside Omniscio but is off until you switch it on in Marketplace → Installed.
What it is
A retrospective engine. On a schedule you choose, it looks at a window of your recent work — the GitHub pull requests across the repositories you name — and writes a report about what keeps happening: repositories that keep needing fix pull requests, repositories that change constantly, and changes that would remove the repetition. It reads pull request titles, branch names and line counts, never the code. The plugin also describes a session analysis, but that part cannot reach the local session list today, so a report covers pull requests only.
The report is not a chat answer you have to ask for. It is a stored document with a week it covers, so you can read this period and compare it with the last one, and it carries two things a summary usually does not: patterns, each with a category, a severity, the evidence behind it and a recommended change; and insights, ranked, each marked actionable or not. A pattern that recurs in a later report keeps its identity rather than arriving as a new one, so "is this getting better or worse?" is answerable.
Because a run spends real money at the model provider, the plugin has a per-analysis cost cap. The scheduled weekly or bi-weekly run starts on its own within that cap, while an on-demand run that an agent asks for needs your approval first.
Where to find it
- Switch it on in Marketplace → Installed — it ships inside Omniscio, so there is nothing to
install (
plugin-marketplace.mdexplains how built-in plugins differ from Marketplace ones). - Its own screen — once enabled it adds a Pattern Oracle row to the sidebar (brain-circuit icon) and hides the project panel inside it. Reports, their patterns and their insights are read there.
- Plugin settings — its configuration lives in the plugin settings panel
(
plugin-settings-panel.md), the same place any marketplace plugin's options live. - For agents — its CLI routes are listed in
plugin-cli-discovery.mdalongside every other plugin's, and it appears in the app's capability catalogue as a callable action.
How it behaves
It needs its own access to your work. Two things are entered in the plugin's settings, and a third is your own key:
- A GitHub organization and a GitHub personal access token with
repoandread:orgscope, which is what lets it read pull-request data. Without them the plugin skips the analysis. - Your own Claude API key, kept in Settings → Accounts, which writes the report. Without one the report lists the patterns it found and says the written analysis was unavailable. Pull request titles, repository names and counts are sent to Claude to write it, and nothing else of yours.
- The settings also list an Omniscio CLI token, meant for session data. Session data cannot be read today, so the token has no effect.
The tokens are stored as password fields, not plain text.
You choose the window and the cadence. Running weekly or bi-weekly, on Sunday, Monday, Friday or Saturday, over a rolling window of recent PR history (14 days unless you change it, 7 to 90). You can also narrow the scan to specific repositories; leaving that blank means every repository in the organization.
You choose how loud it is. Pattern sensitivity has three settings — only clear signals, balanced, or flag everything — and the plugin's own description of the trade is honest: higher means more findings and more noise.
Every run is capped. A run calls the model API and spends money, bounded by the cost cap per analysis you set (two dollars unless you change it). An on-demand run that an agent triggers is gated behind an approval in your inbox, while the scheduled run starts on its own within the cap.
You can close the loop. A pattern's recommendation has its own tracking status, so a recommendation can be marked resolved — which is what makes the next report's "still open" and "addressed" counts mean anything. Individual patterns and insights can also be dismissed.
Related
How plugins are found, installed and enabled is on Plugin marketplace, and where a plugin's own options live is on Plugin settings panel. The CLI-route surface this plugin's one action appears in is Plugin CLI discovery, and how a plugin adds a sidebar row like this one is on Plugin UI access.
Last verified 2026-11-05