Spend Gate, Tripwire & Intelligence Toggle Issues
Spend Gate — blocked banner appears at the top of Orbit
Section titled “Spend Gate — blocked banner appears at the top of Orbit”When your daily Sivants-billed spend reaches the hard ceiling, Orbit shows a persistent red banner:
Daily Sivants spend limit reached ($X.XX of $Y.YY). Spending is paused until midnight (America/New_York).
While this banner is active, all Sivants-billed calls are rejected. BYOK calls (your own Anthropic, OpenAI, or other provider key stored in the Vault) are never blocked — they bypass the gate entirely.
To unblock immediately: click Raise ceiling for today in the banner, or call POST /api/spend-gate/raise-ceiling. This grants a same-day override — spend above the ceiling is allowed for the rest of that calendar day. The override expires at midnight and the gate resets to its configured thresholds automatically.
To check the current state without the banner: GET /api/spend-gate/state returns the current zone, today’s spend, and both threshold values.
Spend Gate — amber banner (over soft cap, drawing from credits)
Section titled “Spend Gate — amber banner (over soft cap, drawing from credits)”An amber banner at the top of Orbit means your daily spend has crossed the soft cap but has not yet reached the hard ceiling. Calls are still going through, but they are now drawing from your Sivants Credits balance instead of being covered by your subscription.
This is expected behavior. If you want to avoid drawing credits, either pause Sivants-billed calls for the day or raise the soft cap in Settings → Billing & Spend.
Spend Gate blocks unexpectedly on BYOK calls
Section titled “Spend Gate blocks unexpectedly on BYOK calls”The Spend Gate only applies to Sivants-billed calls. If your call uses a key stored in the Vault (Anthropic, OpenAI, Google, etc.), the gate never touches it. If a BYOK call appears to be blocked, check that the key is actually being resolved from the Vault — confirm with orbit_vault_list that the key is present and named correctly. A missing or misconfigured key can cause the call to fall through to the Sivants proxy, where it would then be gated.
Tripwire alert fires unexpectedly
Section titled “Tripwire alert fires unexpectedly”The Tripwire fires a persistent banner when any model outside the Sivants-covered allowlist generates a billing event. Common causes:
- A prompt’s
model:override tag points to a model that is not on the covered allowlist. Check the tag on recently queued prompts. - A tier in Settings → Model Tiers & Agents is pointing at a non-covered model. Review every tier assignment and confirm each maps to a subscription-covered model.
- A BYOK call billed through your own provider key and triggered the Tripwire because that model is not on the Sivants allowlist. BYOK charges go to your provider, not Sivants, so the Tripwire is informational in this case — you can dismiss the banner.
The Tripwire does not block calls. It only alerts. After you’ve identified and resolved the routing mismatch, dismiss the banner manually.
Expected background summaries or checks are not running
Section titled “Expected background summaries or checks are not running”Intelligence Toggles are per-category switches that fully suppress specific background AI calls. When a toggle is off, no API request is made — the call is silently skipped. If you notice that completion notes are not being enriched, reference docs are not updating, or daily summaries are not appearing, check the toggle state at Settings → Intelligence → Automatic summaries & updates.
The toggles and what they suppress:
- Code-impact pre-checks — pre-flight analysis run before a prompt executes. Off means no pre-check call.
- Completion-note enrichment — Orbit AI expands the raw completion notes after a prompt ships. Off means notes are written exactly as the agent produced them.
- Reference-doc auto-updates —
context/orbit-reference-delta.mdis updated automatically after features ship. Off means the delta log is never touched automatically. - Handoff profile / README updates — the project handoff document and AI_README are refreshed after significant changes. Off means no automatic updates.
- Daily-summary narrative & patterns — drives the Story and Patterns tabs in the Daily Summary modal. Off means those tabs are empty or show stale data.
- CLAUDE.md drift checks — periodic comparison of CLAUDE.md against recent agent behavior. Off disables those checks entirely.
Each toggle shows a Saving… indicator while persisting. Changes take effect immediately on save — there is no lag.
Prompt review calls are not what you expect
Section titled “Prompt review calls are not what you expect”The Prompt review row in the Intelligence settings is read-only — it shows the current gate setting but is configured separately in Settings → Workflow / Model Tiers → Prompt Review. This is the highest-volume background spender. If you use a BYOK key, each review call bills your provider directly. To reduce review volume, change the review gate setting in the Model Tiers UI, not in the Intelligence panel.