The gate only ran in CI, so a hand-numbered or badly named migration was caught
minutes after the push. The hook now lists the staged paths under
src/lib/db/migrations/ and, only when there is one, runs
scripts/check/check-migration-numbering.mjs (names, duplicates and the frozen
001-241 series; the comparison with the base stays in CI). It runs before
lint-staged, aborts the commit if git cannot list the staged files, and blanks
GITHUB_EVENT_NAME / MIGRATION_BASE_REF so a CI-like environment never turns the
local run into a base comparison.
Tests: the hook test now mocks git, pins the step's placement and gating, and
runs the real hook text with real git and the real gate in a throwaway
repository (bad name fails with the gate's message, good name passes, no
migration staged never runs the gate).
Closes#20578
* feat(ci): omni-queue owner voice and signed merge commits, both off
Owner voice (config `voice`, default "app"): with "owner", the queue's
comments and label removals on pull requests, the dashboard issue and its
comments, base-red comments and the tree-divergence issue go out with
OMNI_QUEUE_LAND_TOKEN (scripts/merge-queue/voice.mjs). Reads, commit
statuses, refs, the state branch and re-runs stay the App's. A missing
token or a 401/403 retries the same write with the App's token and records
one error event per tick. commentOnce trusts markers by the App or by the
owner's login read from the token itself (GET /user).
Signed merge commits (config landing.signing, default "none"): with "ssh"
and landing.actor "owner", composeCandidate signs every merge commit with
the key the tick job writes from the OMNI_QUEUE_SIGNING_KEY secret to a
0600 file under RUNNER_TEMP (removed by an always() step). git gets the
path as per-command configuration through the environment. A missing key
or a failed signature composes unsigned and records one error event per
batch.
The shipped config keeps both off and mode shadow.
* docs(changelog): add the fragment for the omni-queue owner voice and signed merges (#20792)
* test(ci): compare the signed commit's committer by prefix, not a built regex (#20792)
The retired-asset audit in provider-assets-generic-fallback.test.mjs walked the
working tree at module load and read every text file whole. In the omni-queue
base check, "Fast Quality Gates" builds config/quality/test-impact-map.json
(gitignored, ~556 MB on release/v3.8.55) before running the whole unit suite,
and readFile(path, "utf8") on it threw "RangeError: Invalid string length"
(run 44795004759).
The audit now lists files with git ls-files (same scope rules; the old walk
stays as the fallback for a tree without git metadata), reads each file with a
64 MiB bound, and reports oversized or unreadable files by name instead of
aborting. A regression test builds a temporary git repository with an
untracked 600 MB sparse file in a walked directory.
CodeQL flags js/resource-exhaustion when a timer delay comes from
configuration without a visible upper bound at the call. The value was
already clamped to 100-5000 ms by the schema and clampDecisionTimeout,
but through a helper the analysis does not follow. Compare against
MAX_DECISION_TIMEOUT_MS where the timer is set (and where the transport
receives its timeout), so the bound is explicit. Behavior is unchanged.
* fix(gamification): commit one XP award as a single transaction
An authenticated request ran six autocommit statements per award: addXp inserted
xp_audit_log and upserted xp_action_counts and user_levels, then
updateRewardScores upserted leaderboard for global, weekly and monthly. Each took
the writer lock and its own commit, and a failure between them left XP without a
score or the reverse.
awardXp wraps addXp and the leaderboard upserts in one db.transaction.
emitGamificationEvent and the bonus-XP path (streak_bonus, badge_unlock) use it,
and the leaderboard credit now follows the award directly. Anti-cheat still runs
before any write; the lifetime action counter, one-time badge and streak-bonus
guards, tokens_shared scope and score values are unchanged. No setting or
delayed batch is added, so no award can be lost on shutdown.
Finding: ordata-48.
(cherry picked from commit a6517e5416cfbbb8e692767e68b0548dce931369)
* perf(db): compute the migration 044 key backfill once per connection
The old statement ran two correlated GROUP BY / ORDER BY subqueries for every
usage_history row that missed api_key_name, so the cost was the missing rows
times the history of their connection. The most used name and id of each
connection now go into two temp tables once, and the update joins them. The
values filled are the same: the most used non-empty value wins, a count tie
goes to the greater value, name and id are picked independently, a row with no
connection is not touched, and an unknown connection stays empty. Only installs
that have not run 044 yet see the change.
Finding: ordata-92.
(cherry picked from commit cb61850859b9e571c6cfbc6471349bdbb0048f54)
* fix(usage): retry a locked usage write on a backoff before dropping the row
A usage row that met a locked database was retried once after 1 s, then
dropped with one console.error. The 2 s busy timeout is not waited on the
first attempt, so a second writer process (CLI, desktop host) that holds the
lock for a few seconds lost the billing row.
The usage writer now retries on a 1, 2, 4, 8, 16 s backoff (about 31 s in
all), off the request path as before. Non-lock errors are still logged at
once and never retried. The generic one-retry scheduler used by call logs
and proxy logs is unchanged.
Finding: sub2api-86
(cherry picked from commit 93dd20bdd69b5cc23d836575c93c03172edca1f8)
* fix(quota): a stale exhausted sample with no reset no longer pauses an account
An exhausted quota window that carries no future reset time and was last seen
more than 2 hours ago now reads as unknown, not as reached. A paused account
receives no fresh quota headers, so one old sample kept it paused forever.
A window with a future reset still pauses until that reset, and a window seen
within 2 hours still pauses.
Finding: sub2api-43.
(cherry picked from commit e0b51b8052e42e475e8554d904b3f96223f181a1)
* fix(usage): add a late row to a purged day's rollup instead of replacing it
The retention job rolls usage_history up into daily_usage_summary, then deletes
whole days. The next rollup replaced a day's summary with the raw rows it still
found, so one row that arrived late for a purged day erased that day's earlier
totals (3 requests became 1 in the probe).
The purge now records the day it reached and the highest row id at that time in
one key_value row (no migration). A row below that day with a higher id is late:
the rollup adds it to the day's summary and moves the recorded id forward in the
same transaction. A second rollup that read the same rows finds the mark changed,
rolls back, and reports an error, so the caller keeps its raw rows. Days that are
not purged yet are still recomputed from their raw rows.
Finding: sub2api-82.
(cherry picked from commit 449f4f3b10f117e2e25716abd302ee0641949968)
* chore(changelog): name the new fragments 0000-<slug> for the publisher
* refactor(db): move the usage purge day recording into two helpers
The late-row member adds a branch and a transaction to deleteWholeDaysBefore.
That raises its cognitive complexity from 0 to 1 over the base. Two small helpers
keep the function at its old complexity. No behaviour change.
* docs(changelog): number the fragment (#20226)
* chore: drop derived values the release refresh now owns
Plan 2026-11-13 (derived numbers resolved only at release): feature PRs no longer write values
that depend on the state of the base. This commit restores the lines this PR changed only to
update such values (counts in docs, the llm.txt mirrors, the Stryker test list, the package
description, counts in agent-instruction files) to the text of the PR's merge base, so merging
the current base brings the values `npm run release:refresh-derived` maintains. Every other
change of the PR is untouched.
* test(usage): stop waiting for a MockTimers warning newer Node versions never emit
The retry test waited at the top level for the experimental-feature
warning that the first mock.timers.enable() prints, so a later test that
counts console.error lines would not see it. Node 24 (the CI runtime) no
longer emits that warning, so the wait never settled and the runner
failed the whole file with 'unsettled top-level await'. Wait one
macrotask instead: on versions that still warn, the warning (queued on
process.nextTick) has passed by then; on versions that do not, the wait
ends at once.
* revert(quota): drop the stale-sample no-pause fix from this bundle
Reverts 9a2da1815d (fix(quota): a stale exhausted sample with no reset no
longer pauses an account), with its changelog fragment and test.
Replaced by a separate PR with a per-session/opt-in design (see the PR list); dropped here so the two do not conflict.
* fix(usage): bound late rows to the read max id and check the purge mark on every rollup write
- The late-row branch of the rollup SELECT is bounded by the MAX(id) it read,
so a row another process commits between the two reads waits for the next
run instead of being counted now and again after the mark moves to maxId.
- A rollup transaction that only replaces summaries now checks the purge mark
it classified the days with and rolls back when a purge or a late-row add
moved it, so a stale read cannot overwrite a day that gained late rows.
* revert(db): drop the migration 044 backfill rewrite from this PR
044 is a merged migration: databases that already recorded it never run the new SQL, and a merged migration keeps its content. Removes the SQL change, its changelog fragment and its test, as the maintainer asked. The other changes in this PR are unchanged.
---------
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
check:complexity-ratchets (new-code mode) flagged five new violations:
selectAsync, the combo-model decider, resolveDecisionApiKey (cyclomatic
17 > 15) and DecisionModelSection (289 lines, complexity 16). The
pre-decider checks and the answer checks of the strategy, the
preconditions and in-scope dispatch of the combo-model decider, and the
referenced-connection branch of the credential resolver move into
helpers; the builder section is split into settings, descriptions, test
and preview-hook pieces. Behavior is unchanged: the decision unit tests
and the builder UI tests pass as before.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Co-authored-by: Alvin T. Veroy <551419+alvinveroy@users.noreply.github.com>
Co-authored-by: Rafa Martins <146174365+rafacpti23@users.noreply.github.com>
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
Step 12 and integration: AUTO-COMBO.md gains the `decision` strategy
section (deciders, fields, flag, what leaves the box, failure reasons),
ENVIRONMENT.md and .env.example list OMNIROUTE_DECISION_API_KEY and the
COMBO_DECISION_ROUTER_ENABLED flag, openapi.yaml documents
POST /api/combos/decision-preview, and a changelog fragment is added.
Code: an upstream-reported model name only reaches the log when it looks
like a model id (no spaces, at most 100 characters); the failure branches
of the decision results name their variant explicitly, because
`strict: false` does not narrow the `ok` union (check:open-sse-typecheck
flagged them).
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Co-authored-by: Alvin T. Veroy <551419+alvinveroy@users.noreply.github.com>
Co-authored-by: Rafa Martins <146174365+rafacpti23@users.noreply.github.com>
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
Caller-supplied poll_interval_ms, timeout_ms and poll_timeout_ms on the
NanoBanana, Magnific, Black Forest Labs and RenderHour image handlers are
clamped (30 s interval, 10 min window) by a shared helper that never
shortens a default. The RenderHour poller passes the request abort signal
to sleep(). applySyntxProviderRules only runs own entries of the rules
table.
POST /api/settings/local-corpus (rootPath) and POST /api/settings/obsidian/webdav
(vaultPath) now require an operator credential (dashboard session or local CLI) through
requireOperatorCredential; API keys of any scope and access tokens get 403. The webdav
route passes alwaysRequireAuth because /api/settings/obsidian is ALWAYS_PROTECTED.
Both roots also refuse the filesystem root, the home directory itself and the system
directories /etc /usr /bin /sbin /var /proc /sys /dev /boot /root (and below), compared
after path.resolve and realpath, with a fixed 400 message. The vault keeps its DATA_DIR
overlap refusal.
isInternalAdmissionBypass() accepted the bypass header together with a
bearer equal to resolveSelfLoopBearer(), which is the deployment env key
when one is configured. That key is an ordinary API key clients hold, so
it proved nothing about where a request came from.
Apply the rule from #19292: only the per-process self-hop token (held in
memory on globalThis, compared in constant time) grants the bypass and
the internal upstream-start cap. The vision bridge describe call, the
only caller that sends the bypass header, now also sends the token; it
only does so for this process's own listener.
Engine: google. Sources: docs/architecture/QUALITY_GATES.md, docs/ops/BRANCHING_MODEL.md, docs/ops/MERGE_TRAIN.md, docs/ops/RELEASE_CHECKLIST.md, docs/ops/RUNNER_BOX.md. 299 mirror file(s). 31 unit(s) failed and were left as they were.
Run: https://github.com/cheaper-inference/OmniRoute/actions/runs/44793361106
Step 10: picking the `decision` router strategy shows a section that
writes `config.decision`: decider (TypeSafe System One, own decision URL,
one of the combo's models), base URL and wire for http, model,
connection ID, timeout (100-5000 ms), minimum confidence, per-model
descriptions with the generated cost-rank text as placeholder, and a
one-off Test decision through POST /api/combos/decision-preview. There is
no API-key field. English strings only in en.json. Adapted from the
#18555 DecisionModelSection and draft helpers.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Step 9: POST /api/combos/decision-preview (management auth) builds the
decision menu and the generated cost-rank descriptions for an unsaved
combo. With a prompt it runs one decision with the unsaved settings,
behind the same COMBO_DECISION_ROUTER_ENABLED flag (off = skipped,
nothing fetched); combo-model decisions only exist inside a live request
and are skipped. The body is validated with a strict schema (no apiKey),
failures are log-safe reasons, and errors go through sanitizeErrorMessage.
Adapted from the #18555 preview route.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Step 8: comboRuntimeConfigSchema now validates `config.decision` and the
decision block under `config.auto` with the strict decision schema: the
decider and wire are closed enums, baseUrl is http(s) up to 500
characters without credentials, query or fragment, model up to 200,
timeoutMs an integer from 100 to 5000, minConfidence from 0 to 1, and at
most 50 descriptions (key up to 300, value up to 1000). There is no apiKey
field: `.strict()` rejects it, so no secret can be stored in a combo.
The rest of `config.auto` stays free-form as before.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Co-authored-by: Rafa Martins <146174365+rafacpti23@users.noreply.github.com>
Step 7: a new `decision` strategy in the Auto router registry, next to
nadir. The combo's decision block (config.auto.decision, or
config.decision for top-level router knobs) names the decider:
systemone, http or combo-model. The answer narrows the pool to the chosen
model and rules picks the connection; every failure falls back to rules
with `decision(<kind>): fallback (<reason>)` in the log line, never a URL,
key, prompt or upstream body.
COMBO_DECISION_ROUTER_ENABLED (default false, warning level caution) gates
every decider: while it is off no decider is built, so no credential is
read and nothing is fetched. The jev strategy and its flag are untouched.
resolveAutoStrategy only forwards the parsed block plus the request seams
(signal, handleSingleModel, combos, allowlist) into the routing context.
New tests pin that combos without a decision block keep exactly today's
order and context with the flag on, and that a decision combo with the
flag off routes like the rules fallback with zero fetch. The flag count
tests and the FEATURE_FLAGS.md catalog move from 126 to 127; the strategy
list test gains `decision`.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
The default setup moved CodeQL 2.27.4 -> 2.27.5 on 2026-11-20; the release/v3.8.55 JS analysis went 236 -> 339 results with the same 87 rules and no code change, opening 101 alerts at once and failing the codeql ratchet on every PR. Owner-authorized temporary ceiling 6 -> 103 while the security wave triages them; a follow-up lowers it to the measured count.
Step 6: one of the operator's own provider models answers the routing
question through the combo's handleSingleModel, the way the fusion judge
runs. Combo references (auto, auto/*, configured combo names, ids without
a provider prefix) are refused; the call is non-streaming, tool-free,
temperature 0 with a 256-token budget and carries none of the client's
system prompt, tools or history; an AsyncLocalStorage depth guard refuses
a decision started inside a decision call; the timeout aborts the target.
Prompt and parser are the OpenAI-chat decision wire from #15641.
Co-authored-by: Alvin T. Veroy <551419+alvinveroy@users.noreply.github.com>
Step 5: an operator classifier at its own URL, on the System One wire
(#18555) or the OpenAI chat-completions wire (#15641: strict JSON system
prompt, extractJsonObject, confidence defaults to 0). The base URL must be
http(s) without credentials, query or hash; a URL pointing at this gateway
is refused (recursion); a failure cools the endpoint down for 30 s; a
choice outside the menu or a refusal is a failure, never a route.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Co-authored-by: Alvin T. Veroy <551419+alvinveroy@users.noreply.github.com>
Step 4: the systemone decider asks TypeSafe through the base client
(#15278). Its key comes only from a stored connection by reference
(connectionId, inside the API key allowlist, the jevAsk pattern) or from
OMNIROUTE_DECISION_API_KEY; a referenced connection outside the allowlist
yields no key and never falls back to the environment. The credential
inventory gains the new call site (class B, like jevAsk).
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
Step 3: the TypeSafe System One client used a bare fetch, read the body
with an unbounded response.json() and followed redirects. It now posts
through the decision transport: safeOutboundFetch with the provider
outbound guard, no retries, redirects refused, a 64 KB body cap and the
same status-only failures. Timeouts, results and the jev callers are
unchanged.
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
Co-authored-by: Rafa Martins <146174365+rafacpti23@users.noreply.github.com>
Step 2: every network decider leaves through one path. safeOutboundFetch
with the provider outbound guard, no retries, redirects refused
(redirect "error" on the seam, allowRedirect false on the fetch), a body
read capped at 64 KB, one timeout over the whole round trip, caller abort,
and status-only failures so an upstream body never reaches a log.
Co-authored-by: Rafa Martins <146174365+rafacpti23@users.noreply.github.com>
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Step 1 of the unified decision routing: the shared types every decider
returns (never throws, log-safe failure reasons), the menu of unique pool
models with operator or cost-rank descriptions, the bounded extractor of
the last user message (chat/Claude messages and Responses input; never the
system prompt, tools or instructions), and the anti-recursion header.
Co-authored-by: Marcel Rösler <3178520+BelphegorPrime@users.noreply.github.com>
Co-authored-by: Alvin T. Veroy <551419+alvinveroy@users.noreply.github.com>
#18336 dropped the lcov reporter from the coverage merge on pull_request while SonarQube was off; once vars.SONARQUBE_ENABLED came back, the scan found no coverage/lcov.info and every PR showed 0.0% coverage on new code. The merge step now writes lcov on a PR when SonarQube is enabled (measured cost: none beyond runner variance), and the sonarqube job fails before the scan when the file is missing. Closes#20725.
On the Firecrawl cloud endpoint, a wait_for_selector that is a plain
non-negative integer is now sent as the v2 waitFor delay in milliseconds,
capped at the v2 limit of 60000. Any other value still goes through the
wait action as a CSS selector. Self-hosted base URLs keep the v1 body.
The mapping moves into applyWaitForSelector() so firecrawlFetch does not
grow. Adds the changelog fragment for the v2 scrape migration (#19636).
Grafted from #19799 (numeric waitFor handling and changelog entry), with
the integer-only rule and the 60000 ms clamp from the review.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
New feature flag PLUGIN_PERMISSION_MODEL_ENABLED (security, default off).
When it is on, pluginManager.activate() asks loadPlugin() to start the plugin
host with the Node.js permission model, built from the manifest by
buildPermissionModelArgs() (src/lib/plugins/permissionModel.ts):
- --permission (accepted by Node 22.22+, 24 and 26);
- --allow-fs-read for the generated host script and the plugin directory,
plus the plugin data directory (plugin-data/<name> next to the plugin root)
when file-read or file-write is declared;
- --allow-fs-write for the data directory only when file-write is declared;
- --allow-child-process only when exec is declared.
Workers, addons and WASI stay denied. network stays declarative because the
Node.js permission model does not gate outbound network access. With the flag
off the host argv and env are exactly as before.
PLUGIN_SDK.md gets a flag-off / flag-on permission table, PLUGIN_MARKETPLACE.md
and FEATURE_FLAGS.md document the flag, and the flag-count tests move to 127.
Apply the #20567 status contract to the subscription/plan quota text
signals ("usage limit reached", "plan limit", weekly/session usage
limits). On a 400 such a phrase now counts only with a structured
credit/quota code or for the message-only allow-listed providers
(command-code, bai, openai-compatible-*), so a phrase repeated from the
request no longer classifies as QUOTA_EXHAUSTED or puts a shared LLM or
search connection on hold. 429, 403 and every other status are
unchanged.
The status rule is extracted from isCreditsExhaustedForStatus into
quotaTextSignalCountsForStatus and reused by the classifier, the
fallback engine and the search cooldown.
POST /api/plugins/marketplace/install downloads plugin code and may activate it,
so it now requires the management credential in every auth mode
(alwaysRequireAuth), like POST /api/plugins.
PUT /api/plugins/[name]/config now validates the body with
validatePluginConfig(): only keys declared in the plugin's configSchema are
stored, with type, range and enum checks. A plugin without a configSchema has
no configurable keys, so the write is refused with a fixed 400 and nothing is
stored.
Exclusion is decided before the account-cooldown check, so an account that
the fallback loop just excluded could turn its short model lockout into the
reported model cooldown even while the account itself was cooling down for
much longer, and the caller would retry too early. Count an excluded account
only when it is not in an account cooldown, with the regression test from
#20249.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
* chore(ci): retire the Mergify merge queue
The owner retired Mergify from the merge process on 2026-11-19.
- .mergify.yml: drop the release and relay-integration queue rules and
the queue-label cleanup rule; keep the file with commands_restrictions
that refuse every Mergify command that merges or rewrites a PR, since
with no configuration Mergify's implicit queue still merges on
@mergifyio queue.
- dry-run-lts-cut G11 now checks omni-queue: valid config at the source,
bases managing the release branch, mode live, label present.
- Dated notes on the Mergify-era docs; G11 rows updated.
* docs(changelog): add the fragment for the Mergify retirement (#20616)
* chore(quality): record the retired Mergify contract in the test-masking allowlist (#20616)
* fix(release): sync-next-cycle opens a PR instead of pushing to the release branch
release/vX+1 is the default branch and ruleset 21899981 (Require PR on
default branch, no bypass actors) refuses a direct push, so the final
push of the sync-back could never land. The script now pushes the merge
commit to chore/sync-back-main-<sha12> and opens a PR into the release
branch; it never merges it. Re-running after the side branch reached
origin prints the open PR (or opens it) and stops. The old push stays
behind --direct-push (off by default). The sync worktree is detached at
origin/<branch>, so the merge commit never moves a local release branch
ref. The release-green gate and --skip-green-gate are unchanged.
* docs(changelog): add the fragment for #20645
* test(release): compare the sync-back next-steps line exactly (#20645)
The text form of the usage command (@@om-usage and the plain
/api/usage/om-usage) now applies the same account rule as the JSON form:
a key without self:account-quota or a management scope sees only its
personal quota, and the shared provider accounts are not read for it.
Keys with self:account-quota, management keys and the environment key
keep the provider quota.
"different targets share the existing request wait allowance" had two timing
faults with ~110-320 ms of slack each:
- A wait is granted only when (cooldown end - now + 50 ms) <= maxWaitMs. With a
480 ms cooldown and maxWaitMs 480, a stall that delayed the cooldown write until
the reread made the first wait ~530 ms, so the first target stopped without
spending the allowance and the second used it (200 !== 502).
- A stall after the write let the 480 ms cooldown lapse before the reread
(~160 ms later), with the same result.
The cases now use a 2 s cooldown and, for the budget variant,
maxWaitMs = budgetMs = 2.6 s: any first wait fits (1.4-2.05 s under a 500 ms
stall on either side) and what is left never covers a second one.
Reproduced on the old file with injected stalls (250 ms before the write: the
budget variant fails; 520 ms after it: both fail) and passing on the new one in
all three conditions, together with control runs that give room for two waits
(default limits, and budgetMs 5.2 s): both targets then wait and the request
succeeds (200, four calls), so the 502 still comes from the shared limit.
Full file: 69/69.
Additive merge of cheaper-inference/OmniRoute release/v3.8.55; retain upstream's equivalent VS Code Terra effort recognition and keep provider catalog changes focused. Upstream's existing translated-doc whitespace is outside the PR delta.
The fragment was keyed by the issue number (20250-auggie-cli-quiet-flag.md);
changelog.d fragments are keyed by the PR number, so it becomes
20272-auggie-cli-quiet-flag.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The node tests in this PR exercise the request-body builder, the schema and
the validator directly; on the current base they pass because the fix (#19384)
is already merged. This jsdom test renders AddApiKeyModal for cloudflare-ai,
types an API key and an Account ID, clicks "Check" and asserts the request to
/api/providers/validate carries the trimmed accountId. It fails with the
#19384 change reverted (the body has no accountId) and passes with it.
The changelog fragment is renamed to the <PR>-<slug> convention and moved to
maintenance: the fix itself already has its entry under #19384, so this PR
only adds regression tests.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
Add the resolveModelDisplayName cases from #20114: an explicit name such as
"Custom Label" wins over a dated snapshot id, and the id passed as its own
name is still derived to "GPT-5". Also cover the namespaced
cmc/openai/gpt-4.1-2025-04-14 id.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The existing #20449 case passes on the base too: the entry-relative worker is
found before any module-relative candidate, so the guard is never exercised.
This case leaves only a cwd-relative TypeScript worker, so the base (which
ignores moduleUrl and keeps using the real module directory) returns the
source tree's worker, while the fix skips every module-relative candidate and
probes only the cwd layout.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fragment was named api-key-usage-limits-long-context-20153.md;
changelog.d fragments are keyed by the PR number first, so it becomes
20255-api-key-usage-limits-long-context.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The five wall-clock assertions used a 250 ms budget, which a loaded CI runner
can exceed even with the linear fix. The pre-fix regexes take tens of seconds
on the same inputs, so a shared 2 s budget still fails on the old code and
passes on the fix. Also names the changelog fragment after PR #19916, as
changelog.d/README.md asks.
Guards the opt-in contract of targetModels/excludedModels: with both lists unset
or empty, every model is still routed by task type and counted in the stats,
and a persisted config written before #20294 (no scoping keys) hydrates without
adding a scope.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fragment was named cursor-grok-47-standard-speed-20077.md; changelog.d
fragments are keyed by the PR number first, so it becomes
20248-cursor-grok-47-standard-speed.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fallback loop can also pass the account that just failed through the
excludeConnectionIds array option, not only the positional argument. Add a
test for that entry point (adapted from #20249, which used the option name
excludedConnectionIds that getProviderCredentials does not read), and add the
changelog fragment for #20083 based on the wording from #20249.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
The fragment was named dashboard-fmt-compact-boundary-20068.md; changelog.d
fragments are keyed by the PR number first, so it becomes
20113-dashboard-fmt-compact-boundary.md with its content unchanged.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
Exclusion is decided before any quota check, so an excluded account whose
quota for the model is exhausted could still turn its short lockout into the
reported model cooldown, and the caller would retry too early. Count an
excluded account only when its quota still allows the model, with a
regression test where both accounts are exhausted.
check:test-tla-order rejected the top-level await placed between test() calls:
under --test-force-exit the later tests can silently never run (#18045). Move
the combos.ts import up with the other top-level imports.
Keeps resolveCallLogArtifactWorker under the cyclomatic complexity cap
(15) flagged by the complexity-ratchets new-code gate; lookup order and
fallbacks are unchanged.
update() awaited findById() between reading the row and running the
UPDATE, so two overlapping updates of the same rule could both read the
same base row and the second write dropped the first caller's fields.
Read the row synchronously so the read, merge, reference check and write
cannot interleave.
A count of 64 candidates let short decoy hex runs placed first use up the
budget, so a base64-encoded instruction after them was never decoded.
Budget decoded bytes instead, sized above what the 16 KB scan text can
produce over both layers, so no candidate is skipped. Covered by a
failing-then-passing decoy test plus a cost test for a text packed with
readable encoded runs.
targetModels/excludedModels now cover the exact id plus its ":" variants
and "/" children, so scoping openai/gpt-4o no longer captures
openai/gpt-4o-mini (#20294).
The bounded `.{0,N}?` repeats still backtracked when a long whitespace run
followed SELECT, import or if (SELECT plus 140k spaces took ~2 s; if plus
140k spaces did not finish), and they stopped scoring valid spans longer
than the cap.
Count the import/SELECT/${} indicators with a linear scan that keeps the
old greedy one-per-line semantics, and make the if ... then condition start
at a non-space so no two whitespace quantifiers overlap. Each span indicator
is now asserted on its own, including spans past the old caps.
- Reject `compaction_trigger` on Chat Completions targets again: Codex remote
compaction v2 needs exactly one `compaction` output item, which a Chat upstream
cannot return, so skipping the marker answered with an unusable normal turn
(and a trigger-only input produced `messages: []`).
- Restore readable compaction items with role-aware text parts (`output_text`
for assistant), so the Codex normalizer no longer forwards assistant history
as `input_text`.
- Accept only non-blank string content or a non-empty part array, falling back
to `text`; other shapes are no longer forwarded as Chat content.
- Split restoreReadableCompactionItem into helpers (complexity ratchet).
Refs #19730
The new vertex default rows copied Pro rates onto gemini-3-flash-preview
($2/$12 instead of $0.50/$3), used a flat $2/$12 for gemini-2.5-pro
(Google bills $1.25/$10 up to 200K prompt tokens and $2.50/$15 above),
and set the 2.5 Flash Lite cached-input rate to $0.025 instead of $0.01.
Add the long_context tier for 2.5 Pro and a test that pins the rows.
Conflict in src/sse/services/auth.ts (imports only): keep isExpiryFirstDeadlineOrder
from this branch and isWorkspacePolicyBudget429 from #19314.
expiry-first-combo-ordering case 8 (#17829) pinned the old reading of a lapsed
reset as maximally urgent. With this PR a lapsed weekly reset counts as a refilled
window rolled forward one period, so the expected score is 1/167 instead of 3.2.
Plan 2026-11-13 (derived numbers resolved only at release): feature PRs no longer write values
that depend on the state of the base. This commit restores the lines this PR changed only to
update such values (counts in docs, the llm.txt mirrors, the Stryker test list, the package
description, counts in agent-instruction files) to the text of the PR's merge base, so merging
the current base brings the values `npm run release:refresh-derived` maintains. Every other
change of the PR is untouched.
Plan 2026-11-13 (derived numbers resolved only at release): feature PRs no longer write values
that depend on the state of the base. This commit restores the lines this PR changed only to
update such values (counts in docs, the llm.txt mirrors, the Stryker test list, the package
description, counts in agent-instruction files) to the text of the PR's merge base, so merging
the current base brings the values `npm run release:refresh-derived` maintains. Every other
change of the PR is untouched.
Plan 2026-11-13 (derived numbers resolved only at release): feature PRs no longer write values
that depend on the state of the base. This commit restores the lines this PR changed only to
update such values (counts in docs, the llm.txt mirrors, the Stryker test list, the package
description, counts in agent-instruction files) to the text of the PR's merge base, so merging
the current base brings the values `npm run release:refresh-derived` maintains. Every other
change of the PR is untouched.
The multi-key and solitary-thought branches pushed consumePlanningLeak
over the cognitive-complexity limit (complexity-ratchets new-code 0 -> 1).
Extract classifyUnclosedObject, isSolitaryThought and
classifySolitaryThought; behavior is unchanged (the repeated top-level
comma check in the unclosed branch was already covered by the early
return).
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
#19384 already landed the same accountId forwarding in the validate
request body, the Zod schema and the route. Merging the base made both
copies coexist (duplicate accountId keys in an object literal and in the
schema), so drop this branch's duplicates and keep the base code; the
regression tests pass against it unchanged.
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
During fallback, the account that just failed is excluded from the retry and
tagged "excluded", so the #18664 branch (which only checked "modelLocked")
skipped its short retryable lockout. When every other account was
quota-exhausted, the request was reported as "All <provider> accounts have
exhausted their quota" with a reset minutes or days away, and clients backed
off for that long although the healthy account recovered within seconds.
Also consider "excluded" connections in that branch. Excluded connections
without an active retryable lockout are still ignored.
Fixes#20083
v2 scrape reads waitFor as a millisecond delay, so the selector string cannot
go there. The v2 actions list has a wait step that blocks until a CSS selector
is visible, which is what the field meant. A self-hosted base URL still speaks
v1 and keeps the selector in waitFor.
Signed-off-by: Minxi Hou <houminxi@gmail.com>
Firecrawl shuts its v1 API down on 2026-12-10 and answers it with HTTP 410
after that. Search, map and credit usage already call v2. The page fetch and
the dashboard key probe were the two calls still posting to /v1/scrape.
The cloud host now posts to /v2/scrape. v2 scrape rejects maxDepth outright and
treats waitFor as a millisecond delay, so the depth and CSS selector fields
stay on our own request but are no longer forwarded to the cloud. A
self-hosted base URL still speaks v1, so it keeps /v1/scrape and both fields.
Fixes#19636
Signed-off-by: Minxi Hou <houminxi@gmail.com>
Tavily added max_age_hours in October 2026 so a search can cap how old the
cached copy of each result is: 1 to 720 hours, 0 to always fetch live, -1 to
never fetch live. The provider_options bag drops any key that is not on the
allow-list, so callers had no way to send it.
The field now passes through with that exact value set, and anything outside
it (721, a fraction, a string) is dropped instead of forwarded.
Signed-off-by: Minxi Hou <houminxi@gmail.com>
The follow-up leg of a non-streaming server-owned tool loop re-translates the next
source body without antigravitySessionKey, so it fell back to the account-wide
sessionId and could evict a parallel conversation's cache. chatCore now resolves
the key once at function scope and passes it to runNonStreamingResponse, whose
follow-up translation forwards it. Adds docstrings for the session helpers.
Review: CodeRabbit on #19876.
knip flags ReasoningEffortMode, ReasoningRuleScope and ReasoningTargetKind as
new dead exports in the touched facade. No importer uses them through
src/lib/db/reasoningRoutingRules; they remain exported from the domain
repository contract.
The OpenAI->Antigravity envelope derived request.sessionId from the account
email alone (#13305), so every conversation running in parallel on one
account shared a single Cloud Code session. Parallel coding-agent tasks then
evicted each other's prompt cache: on a live 8-task opencode run against
gemini-4-carbon-medium, tokens_cache_read collapsed from ~280k to 10,443/None
and 250k-380k uncached prefills took 250-589s (two 600s pre-header 504s),
while the same conversation alone on an account finished 255k-271k cached
turns in 11-14s.
chatCore now passes the resolved conversationId (falling back to the
session-affinity key) into translateRequest as antigravitySessionKey, and the
envelope hashes account + conversation. One conversation keeps one stable
session across turns (cache reuse is preserved), parallel conversations get
distinct sessions, and requests with no conversation key keep the old
account-derived id.
An OpenAI-format tool loop sent to Claude ends with the results of the last
assistant turn's tool calls. They sit after that turn's cache breakpoint, so
they are billed as fresh input, and the next call sends them again.
prepareClaudeRequest rebuilds every message marker, so the policy must live
there. Add markFinalToolResults: when the final user turn holds a tool_result
and fewer than 4 markers exist, mark its last block with the tail marker (same
5m class as the other tail markers). The next call then reads those tokens
from cache at 0.1x. A request with no follow-up pays a one-time 0.25x write
premium on those tokens. Client-managed (passthrough) markers are not changed,
and the 4-marker limit still holds: enforceCacheControlBlockLimit and the new
helper share one marker walk.
resolveProviderId calls getProviderByAlias, which looped over every
provider section and compared alias and id on each entry. A miss, for
example an openai-compatible-* id, scanned the whole catalog of about
380 providers and then returned the input. Circuit-breaker names,
target gates, quota lookups and failure records call it on every
routing step.
Build one Map from alias and id to provider on first use. A key is
claimed by the first provider in section order whose alias or id
equals it, the same rule as the old scan, so an alias that equals
another provider's id (poe) keeps resolving as before. Only the
internal lookup changes: ALIAS_TO_ID and getProviderById are untouched.
(cherry picked from commit a95c42fda203fabf12cf226431340d1c2c6f57f1)
The custom PII pattern gate relied on safe-regex alone. safe-regex is a
static star-height check and accepts overlapping alternations such as
(a|aa)+$, which take exponential time on a run of one character. Such a
pattern passed save, preview and runtime compile, then froze the event
loop on the first matching text.
After the static check, run the pattern on seven 64-character runs
(letter, non-ASCII letter, digit, space, dash, underscore, dot) under a
100 ms vm deadline. A pattern that is cut off is refused as unsafe.
The same gate covers save, preview and the runtime skip of stored rows.
(cherry picked from commit e45b0378848f3428ce7d9ae62b63641cc4e50370)
A HALF_OPEN circuit breaker closed on the first probe success, whatever
`halfOpenRequests` was. One lucky probe could restore a flapping
provider, and the setting had no effect above 1.
The breaker now counts probe successes in the HALF_OPEN episode and
closes when `halfOpenRequests` of them have passed. A probe failure
still reopens the breaker. The count resets on every state change and
when a stale probe lease is renewed. The default (1) behaves as before.
(cherry picked from commit f2d231c43c41ed330d733231fe4ffb812d16d91d)
detectInjection matched the surface text only. "Ignore all previous
instructions" wrapped in base64, hex or percent-encoding passed the guard
with no detection, even in block mode. The only rule that mentioned encoding
(encoding_evasion) needs the words "base64 decode" next to "instruction".
detectInjection now also decodes encoded runs in the scanned text, to two
layers, and runs the injection patterns on what they decode to. A hit keeps
the rule's severity and is reported as "decoded:<rule>", so the block
threshold, logging and the guard treat it like the plain form.
Bounds: the input is still the 16 KB scan window. A run needs 24 base64
characters or 12 hex bytes, at most 64 decode attempts run per request, and
a run that decodes to binary (a hash, a token, random data) is dropped. The
run patterns are single character classes, so they are linear. Worst case on
a 16 KB window is about 0.6 ms in the benchmark, and no benign sample (hashes,
random base64, kebab-case paths, form data) produced a hit.
(cherry picked from commit 838f618f8ba16be77af64147a1128eb9075f51fd)
- list expiry-first-deadline-order and -session-spreading tests in
stryker tap.testFiles (they cover quotaScoring.ts and sse/services/auth.ts)
- extract windowUsableCap() from resolveUsableAndReset so the lapsed-window
cap stays under the cognitive-complexity limit (same behaviour)
- move pickExpiryFirstConnection's JSDoc back above its function
A combo edit routed to Leonardo uploaded only the first reference and dropped
the rest, while the single-model route answers 400. The combo branch now
returns the same 400, so the combo moves on to its next provider.
After a strategy picks an account, getProviderCredentials moves the request to
a peer OAuth account with fewer foreign sessions in flight. Under
`expiryFirstOrder: "deadline"` that undid the decision: on a two-account
Claude pool every parallel Claude Code conversation after the first was moved
to the account whose week resets two days later, so it kept being spent.
Deadline order now keeps its pick; the default rate order still spreads.
A session whose reset already passed was only skipped when a longer window
existed. For a session-only account the past reset stayed negative and its
stale fraction still capped `usable`, so deadline order ranked it as already
expiring. A lapsed session is now refilled with its next reset one 5h period
later, like weekly and monthly windows. Adds two regression tests.
A longer quota window whose reset already passed comes from a stale quota
read. expiry-first scored it as "expires now" (deadline floored to
minHours), so a stale account looked like the most urgent one and took the
traffic: on 2026-11-06/07 a Claude Team account whose last read still carried
the previous Friday's weekly reset drained ahead of a Max account resetting two
days later. A lapsed weekly/monthly window is now treated as refilled, with its
next reset one nominal period later; a lapsed window of unknown length keeps no
deadline.
Adds `expiryFirstOrder: "deadline"` (provider override or global): accounts
that still hold quota are spent strictly by the nearest deadline, a spent 5h
session or exhausted window is skipped until it refills, and deadlines within
`expiryFirstDeadlineTieMinutes` (default 60) rotate least-recently-used. The
default stays the per-hour rate. Provider strategy overrides now reach the
expiry-first config, and the settings schema accepts both keys per provider.
/v1/images/edits passed only the prompt to the Leonardo handler, so every
edit came back 1024x1024 whatever size the client asked for, while
/v1/images/generations already maps size to width/height. Pass size on the
single-model and combo edit paths; the route test now asserts 576x1024.
The release now downloads Leonardo results through the guarded media fetch
(DNS resolve + pinned agent), so the edit tests stub the lookup and the pinned
fetch the same way the other Leonardo tests do, and wait for call-log saves
before closing the DB.
/v1/images/edits rejected every Leonardo model, although Leonardo does
image-to-image on its generations call. Upload the edit reference through
Leonardo's init-image flow (presigned S3 form post, no Leonardo token sent
to S3) and generate with init_image_id and init_strength 0.3, on both the
single-model and the combo edit paths. Edits are call-logged under
/v1/images/edits.
The video handler posted an image-generation body (modelId "phoenix",
num_frames) to /generations, which Leonardo rejects with 400 "Unexpected
variable num_frames", so leonardo video never worked. Submit to
/generations-text-to-video with a model enum and resolution, read
motionVideoGenerationJob, poll the generations status URL, and download
motionMP4URL (url is a jpg thumbnail). The catalog lists Motion 2.0 and
Motion 2.0 Fast; the old phoenix id maps to Motion 2.0.
Leonardo's v1 generations API takes a platform-model UUID as modelId. The
handler sent the catalog id (phoenix, sdxl), which Leonardo answers with
HTTP 500 "internal error", so every leonardo/* image request failed.
Map phoenix and sdxl to the Phoenix 1.0 and SDXL 1.0 UUIDs; a raw UUID
passes through so any Leonardo model can be used.
echo "::error::coverage/lcov.info is missing or empty after downloading coverage-report; SonarQube would report 0% coverage on new code. Check the lcov reporter in the test-coverage job's merge step (#20725)."
- **feat(images):** `/v1/images/edits` supports Leonardo: the reference image is uploaded through Leonardo's init-image flow and the generation is guided by it (`init_image_id`, `init_strength` 0.3), instead of the edit being rejected as unsupported. Leonardo takes one reference image; more than one returns 400, and a combo moves on to its next provider rather than editing with the first image only ([#18674](https://github.com/cheaper-inference/OmniRoute/pull/18674), closes [#18671](https://github.com/cheaper-inference/OmniRoute/issues/18671))
- **feat(providers):** `expiry-first` treats a lapsed weekly/monthly reset (stale quota read) as refilled instead of "expires now", and gains an opt-in `expiryFirstOrder: "deadline"` (per provider) that spends the account whose quota is lost first while it has quota ([#19583](https://github.com/diegosouzapw/OmniRoute/pull/19583)) — thanks @feci
- feat(routing): allow scoping task-aware routing to specific target or excluded models/combos via `targetModels` and `excludedModels` in TaskRoutingConfig (#20294)
- **feat(plugins):** Opt-in `PLUGIN_PERMISSION_MODEL_ENABLED` feature flag (off by default) runs each plugin process under the Node.js permission model built from its manifest: reads confined to the plugin directory, writes only to its data directory with `file-write`, child processes only with `exec`; `network` stays declarative
- **feat(ci):** omni-queue can speak as the owner and sign its merge commits, both off by default. With `voice: "owner"` in `config/merge-queue/config.json`, the queue's comments and label removals on pull requests, the dashboard issue and its comments, base-red comments and the tree-divergence issue go out with `OMNI_QUEUE_LAND_TOKEN`; statuses, refs, the state branch, re-runs and reads stay the App's, and a missing or refused token falls back to the App with one `error` event. With `landing.signing: "ssh"` (owner actor only), every merge commit the queue composes is signed with the owner's key from the `OMNI_QUEUE_SIGNING_KEY` environment secret, and a missing key composes unsigned with one `error` event per batch ([#20792](https://github.com/cheaper-inference/OmniRoute/pull/20792))
- **feat(combo):** new `decision` router strategy for Auto combos: a decider picks the model for each request and `rules` picks the account. The decider can be TypeSafe System One, your own decision URL (System One or OpenAI chat format), or one of the combo's own models called in process. Only the last user message (up to 8000 characters) and the model menu are sent; the key comes from a stored connection inside the API key's allowed connections or from `OMNIROUTE_DECISION_API_KEY`, never from the combo. Calls go through the outbound guard with no redirects, a 64 KB answer cap and a 2 s default timeout (5 s max), and any failure routes with `rules`. Off by default behind `COMBO_DECISION_ROUTER_ENABLED`; combos without a decision block do not change. The combo builder gets the settings and a Test decision button, and the TypeSafe client now uses the same guarded transport — thanks @BelphegorPrime, @alvinveroy, @rafacpti23 and @miguelenes
- Add an opt-in `X-OmniRoute-Selected-Connection-Plan` response header for Codex account-routing troubleshooting (`OMNIROUTE_CODEX_PLAN_RESPONSE_HEADER=1`), off by default with an explicit plan allowlist.
- **feat(models):** add GPT-6.1 Terra to OpenAI API and Codex model catalogs, including Responses-only tool routing, supported reasoning tiers, verified token pricing, long-context rates, and Codex aliases.
- Move the Firecrawl cloud scrape call and the dashboard key probe from `/v1/scrape` to `/v2/scrape` before the 2026-12-10 v1 shutdown (#19636): a CSS `wait_for_selector` becomes a v2 `wait` action, a plain integer becomes the `waitFor` delay in milliseconds (capped at 60000), and `maxDepth` is no longer sent to the cloud endpoint. Self-hosted base URLs stay on `/v1/scrape` with the previous body.
- **fix(security):** the prompt-injection guard now decodes base64, hex and percent-encoded text in a request and scans the result, so an instruction hidden in an encoded string is scored like the same instruction in plain text. ([#19724](https://github.com/cheaper-inference/OmniRoute/pull/19724))
- **fix(resilience):** a circuit breaker with `halfOpenRequests` above 1 now needs that many probe successes in a row before it closes, so one lucky probe no longer restores a flapping provider. ([#19724](https://github.com/cheaper-inference/OmniRoute/pull/19724))
- **fix(pii):** a custom PII regex that backtracks for exponential time on a long run of one character, such as an overlapping alternation, is now refused when you save or test it, instead of freezing the gateway. ([#19724](https://github.com/cheaper-inference/OmniRoute/pull/19724))
- **fix(translator):** translate Responses `compaction` input items carrying readable content or text into standard Chat messages (assistant summaries keep `output_text` parts) instead of rejecting them. Previously, compaction items without `ocx1:` bridge encryption were rejected with `400 unsupported_feature`, causing combo fallbacks to fail for Responses-native clients. Remote compaction (`compaction_trigger`) still fails explicitly on Chat Completions targets, since they cannot return the required `compaction` output item ([#19730](https://github.com/cheaper-inference/OmniRoute/issues/19730)).
- **fix(antigravity):** parallel conversations on one account no longer share a single Cloud Code session and evict each other's prompt cache — the upstream `sessionId` is now derived from account + conversation ([#19876](https://github.com/cheaper-inference/OmniRoute/pull/19876)) — thanks @adevwithpurpose
- **auto-combo**: Count the `import … from`, `SELECT … FROM` and `${…}` code indicators in `detectCodeComplexity` with a linear scan, and stop the `if … then` pattern in `detectReasoningDepth` from backtracking across long whitespace runs, eliminating quadratic backtracking on long lines without dropping long valid spans (#19881)
- **fix(dashboard):** move the custom banned-keyword editor back to the Resilience settings tab (next to Auto Disable) instead of Security, and harden its save/load path: keywords appear only after the server accepts the PATCH, a failed settings load surfaces an error instead of a misleading empty list, the 200-character limit is enforced in the UI, and removals match by keyword value rather than index. The editor now also stays available when `/api/resilience` fails to load ([#20078](https://github.com/cheaper-inference/OmniRoute/pull/20078)) — thanks @sdfsdfw2
- **fix(sse):** Consider fallback-excluded accounts with short retryable model lockouts when checking remaining accounts for quota exhaustion, returning the short lockout cooldown instead of a multi-hour quota reset; an excluded account that is in an account cooldown or whose own quota for the model is exhausted is still ignored ([#20084](https://github.com/cheaper-inference/OmniRoute/pull/20084), [#20083](https://github.com/cheaper-inference/OmniRoute/issues/20083)) — thanks @bojackduy and @rafacpti23
- Roll over compact count formatting (`fmtCompact`) to `M` and `B` at rounding boundaries (e.g. 999,950 to `1.0M` and 999,999,999 to `1.0B`) to prevent displaying `1000.0K` or `1000.0M` in analytics and dashboard counts (#20068).
- **fix(gamification):** One XP award (audit row, action counter, level row and the global, weekly and monthly leaderboard scores) is now a single SQLite transaction instead of six separate commits per authenticated request, and a failure part-way no longer leaves XP without a score. ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))
- **fix(usage):** A usage row that arrives late for a day the retention job already rolled up and deleted is now added to that day's summary. Before, the next rollup replaced the day's totals with the late row alone and the earlier requests vanished from the analytics. The job records the day it purged to and the highest row id it counted, in one settings row (no migration). ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))
- **fix(usage):** A usage row whose write meets a locked database (for example a second writer process on the same file) is now retried on a backoff for about 31 seconds before it is dropped, not once after one second, so a billed request no longer ends with no usage row. ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))
- Allow standard-speed Grok 4.7 variants (`medium`, `low`, `xhigh`) and bare effort aliases to use standard speed by omitting `ModelDetails` and setting `reasoning_effort`, preventing Cursor from falling back to `grok-4.7-high-fast` (#20077).
- **fix(providers):** remove the deprecated `--quiet` flag from the Auggie CLI invocation arguments ([#20250](https://github.com/cheaper-inference/OmniRoute/issues/20250)). Auggie CLI 1.2+ removed the `--quiet` option, which previously caused all requests to fail with `Error: Unknown option: --quiet` and a 502 status code.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.