🔮Augur v1.5.0

Added

• VisibleProviders A pick weighs how hard the task is. Coding and hard reasoning lean toward Opus, Sol and Grok, and the rest lean toward Sonnet, Luna, DeepSeek and MiniMax, with Opus kept ahead for prose. Fable and Astra are skipped unless named, and a route gets a small lift on what it is known for: MiniMax on long context, Luna on review, ChatGPT on research. --depth deep|everyday overrides the default, each pick ends with a line giving the reason, and a balance section in policy.json changes or switches off the rules.
• VisibleProviders Picks keep Claude on pace. If the week or the 5-hour window is running more than 5 points ahead of the time that has passed, Sonnet is favored over Opus, and if both are running more than 5 points behind, Opus is favored. Once a window hits 90%, optional work goes to other routes when any can take it. If Claude’s figures are missing or old, the pick says it could not check.
• VisibleProviders Backup routes wait their turn. A pick skips Copilot models, and DeepSeek on coding tasks, while any other route can do the work. Copilot’s Anthropic models only come in when Claude is at 90%. Once Copilot’s month passes $150 the pick says so, and at $250 it stops offering Copilot.
• VisibleProviders Picks can suggest more than one model. Most picks also suggest MiniMax for a second look. Research and image tasks suggest a free ChatGPT or Gemini route with the steps to follow, and tagging and typed decisions go to Jev first. Each pick also names the local Laya model as a shadow, so its answer can be compared with the pick’s.
• VisibleProviders augur balance shows what the router is doing. It prints where each kind of work goes now, Claude’s pace, Copilot’s spend and the last few days of picks, and the augur_balance tool returns the same. The service also saves a copy each day in ~/.augur/balance.
• VisibleUI A Balance page in the window app and the terminal app. It shows the same report as augur balance, and nothing on it can be changed. Each provider on the Rules page also carries a chip with its stance: kept on pace, used up first, backup or free. The terminal app’s Settings page moves from key 5 to key 6.

Fixed

• VisiblePlatform The service log records how the service stopped. It used to log every start and no exit, so a service that had died looked the same as one that never ran. Each exit now writes a line with its exit code, and an uncaught error or a stop signal writes its reason first. A kill the service cannot catch, such as an end-task from outside, still leaves no line. The terminal app also starts the service again when it is lost while the app is open.