🔮Augur v1.9.0

Added

• VisibleProviders Codex, Grok and other providers with a usage window now have their own pace. Each one is checked against its 5-hour and weekly windows the way Claude is, so a provider that runs hot leans to its light models and one that runs behind leans to its strong ones. When a window reaches its reserve, the provider’s optional work goes to another subscription, and only Claude’s reserve sends work to a backup route such as Copilot.
• VisibleProviders Pace settings sit in one block per provider. pace.<provider> holds band, reserve, hot, behind and boost, and a provider with no block uses the built-in values. The older claude.* settings still work, and the first save of the rules moves them into pace.claude and marks the balance section as schema 2.
• VisibleProviders A provider with allowance left gets a boost. Its routes score up to 1.5 times higher at a fresh window, less as its fullest window fills, and no higher over the last 10% of that window. A hot provider, one at its reserve, and a route the caller rated below boostFitFloor (0.6 by default) get no boost.
• VisibleProviders Picks are drawn from the odds. Each route’s odds are its score over the sum of the scores still in the draw, so a Preferred route at 2.5 wins against a Normal one at 1.0 about 71% of the time, and a named model always wins. draw.enabled turns the draw off, draw.tail sets how far under the top score a route drops out, and each pick records its odds, whether it was drawn, and the seed.
• VisibleProviders A pick can ask for the top score or mark a snippet. --best on augur pick and best_only on augur_pick take the top score. --snippet and snippet mark a draft of one sentence or one bullet, which is not held to the Opus routes.
• VisibleProviders augur pick-preview shows every route’s odds without drawing. It takes the same arguments as augur pick, prints preview: no draw made and records nothing, and augur_pick_preview shows the odds as well.
• VisibleUI The balance report has a pace row for each paced provider. The providers that need attention come first, each with its windows against pace, its boost and its rough odds. Providers on pace share one group, and those with no usage window are named under Not paced.
• VisibleProviders Jobs can start with standing instructions. A charter folder (runner.charterDir, or charter in ~/.augur) holds core.md, a file per harness under engines and packs under packs, and the service puts them in front of every job’s prompt except on Hermes. charter.json adds packs by rule, and without it write and full jobs get the code pack. --pack and --no-charter on augur run, and packs and no_charter on augur_run, choose per job, and the Service page has a Charter folder setting. With no charter folder, prompts go out unchanged.
• VisibleProviders Codex and Copilot can leave out their own extra context. Setting Harness context (runner.ambient) to trim, or a route’s ambient option, turns off Codex’s optional features and Copilot’s custom instructions and built-in MCP servers, so a job spends fewer input tokens. The default is keep, which changes nothing.
• VisibleProviders A failed job can run again on a fallback route. With Retry on failure (runner.failover) on, a job stopped by a spawn error, a provider limit or a read-only timeout is submitted again on its route’s fallback list, up to three jobs in a chain. A write or full job is retried only for a limit that left no answer and no change. augur wait, augur result, augur run --wait and augur_job follow the chain, and --no-failover stops the retry as well as the fallback at submit. The setting is off by default.
• VisibleProviders Grok and Codex routes keep a named conversation. augur run --conversation <name>, or conversation on augur_run, opens a session on the route, and later jobs with that name resume it. A conversation stays on its route, runs one job at a time and never moves to a fallback, and a resumed Codex conversation keeps its first turn’s tool tier. augur conversations lists them and --forget <name> drops one.
• VisibleUI The window app and the terminal app have a setup interview. A new install opens on it in place of the old settings screen, and Run setup again in Settings opens it later with the current settings filled in. Its steps cover the starting stack (Claude only, several subscriptions, API keys only, or a profile file), the providers and keys, how much of each subscription to hold back and which to use first, pay-per-use spending, and what each model is good at, while a summary lists every setting the answers touch. Nothing is saved until Apply, and a step left alone changes nothing. The last step tests each route that has a key and lists the models still waiting for confirmation.
• VisiblePlatform A profile carries model rules. augur profile export adds a models section with each model’s id, name, activities, data tier, ask first, output, sandbox, effort, cost and data handling, and leaves out its status, pause, notes, thresholds and any field it inherits from its provider. augur profile import checks the whole file first and writes nothing if one entry is wrong. It then adds only the models this install lacks, unreviewed with their rules filled in, so none of them runs until you confirm it in Model rules. A model already here is left as it is and named in the summary, and a provider this install does not know is added for its rules alone. The file stays schema 1, and a profile with no models section imports as it did.
• VisibleProvidersSecurity An agent can add a route with augur_route_add. The tool adds one route and, when asked, its model and a balance reading for a provider that has none. The model arrives unreviewed, and the balance reading stays off until its key is set. A key is never accepted: an option whose name or value looks like a key is refused, as are a route name that already exists and an adapter the service does not have, and a refused add writes nothing. At the Ask me for everything approval level the add is held and nothing is written. The result names the host the route sends its requests to and says that you confirm the model in Model rules and set the key with augur key set <route>.
• VisiblePlatform Laya gives its video memory back while a game runs and after 10 minutes with no request. The server watches for the programs named in LAYA_GAME_PROCS, the two ARK Survival Ascended programs by default, and unloads the model LAYA_GAME_UNLOAD_S seconds (5 by default) after one starts. With no request and no job in flight for LAYA_IDLE_UNLOAD_S seconds (600 by default, and 0 turns it off), it unloads as well, and an idle server then holds about 0.2 GB of video memory in place of about 6 GB. While a game runs the server reports busy and clients use another one. After the game closes or after an idle unload, /load reports ready with the model out of memory, and the next request loads the model before it answers. An unload because other programs keep the card busy still reports not ready, and the model comes back by itself once the card is free. /load also reports unload_reason (busy, game, or idle), idle_s (seconds since the last request), and requests (how many requests the server has taken).

Changed

• VisibleProviders A default install picks differently from 1.8.0. The boost, the draw and the pacing of providers other than Claude apply to every install, including one that names no profile, so the same task can now go to a different model than it did on 1.8.0. Setting pace.<provider>.boost to 1 turns off that provider’s boost, and setting draw.enabled to false makes every pick take the top score.
• VisibleProviders Each provider that serves Opus has its own prose switch. Prose drafting leaves a provider’s Opus route while that provider runs hot and another Opus route can take the work, where before only Claude had the switch.
• VisibleProviders Figures from a provider read less often count for longer. A provider’s figures are ignored once they are two hours old, or one and a half refresh intervals old when the provider is read less often than that, and they are flagged as old after 20 minutes or one and a quarter intervals. Jev’s balance, read once a week, is now weighed in picks until the next read, where before it read “not weighed” two hours after each read. A provider with no known refresh interval keeps the 20-minute and two-hour limits.
• VisibleSecurity augur key set <route> shows where the key will go. When the route has a baseUrl, the prompt and the message after the key is saved name the host the key is sent to, so the address can be checked before the key goes in.