---
title: Pattern Oracle (Plugin)
---

# Pattern Oracle (Plugin)

> **Marketplace plugin** — Pattern Oracle is not built into Omniscio. Install it from the Plugin
> Marketplace and enable it before any of this exists.

## What it is

A retrospective engine. On a schedule you choose, it looks at a window of your recent work —
pull requests across the repositories you name, and your own Omniscio sessions — and writes an
intelligence report about what keeps happening: repeated error shapes, work that keeps hitting the
same snag, and changes that would remove the repetition.

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**
and every run is something a user agrees to rather than something that fires silently.

## Where to find it

- **Install it** from the Plugin Marketplace (`plugin-marketplace.md`) — it is free, category
  `development`, authored by JLS Trading Co.
- **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 route is listed in `plugin-cli-discovery.md` alongside 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 credentials, both entered in the plugin's settings:

- A **GitHub organization** and a **GitHub personal access token** with `repo` and `read:org`
  scope, which is what lets it read pull-request data. Without a token there is no PR side.
- An **Omniscio CLI token**, used to read your own session data. Left empty, it falls back to the
  `AMC_CLI_TOKEN` environment variable.

Both tokens are stored as password fields, not plain text.

**You choose the window and the cadence.** Running weekly or bi-weekly, on a day of the week you
pick, over a rolling window of recent PR history. 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 and confirmed.** A run calls the model API and spends money, bounded by the
**cost cap per analysis** you set. Because of that, triggering a run is gated behind an approval in
your inbox rather than happening on its own.

**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.

## For agents

The plugin's CLI surface (`plugin-cli-discovery.md`) is deliberately narrow: one route that
triggers an on-demand analysis. It is marked as **requiring confirmation**, because it calls a paid
model API — the host asks the user before it runs, with the cost cap in the settings bounding what
that run can spend.

Everything else about the plugin is configuration rather than an action: the organization, token,
repository list, cadence, lookback window, sensitivity and cost cap are settings, and reports,
patterns, insights and recommendation statuses are read from the plugin's own screen.

## Related

How plugins are found, installed and enabled is on [Plugin marketplace](plugin-marketplace.md), and where a plugin's own options live is on [Plugin settings panel](plugin-settings-panel.md). The CLI-route surface this plugin's one action appears in is [Plugin CLI discovery](plugin-cli-discovery.md), and how a plugin adds a sidebar row like this one is on [Plugin UI access](plugin-ui-access.md).