Skip to content

Add an org-wide admin toggle defaulting interactive turns to fast mode - #35

Merged
ReganBell merged 3 commits into
mainfrom
fast-mode-default
Jul 30, 2026
Merged

Add an org-wide admin toggle defaulting interactive turns to fast mode#35
ReganBell merged 3 commits into
mainfrom
fast-mode-default

Conversation

@ReganBell

@ReganBell ReganBell commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Why

With fast mode becoming opt-in (#26), interactive turns outside the web UI (Slack, CLI) never run fast mode — there is no way for an organization that pays for fast-mode quota to make human turns fast by default. This makes that a durable, admin-controllable org setting instead of a hardcoded default.

What

  • New org-scoped boolean setting interactive-fast-mode (default off), following the org-ambient pattern end to end: Postgres-backed interactive_fast_mode_flag table, ScopedConfigStore getters/setters with hydrate/refresh/flush support, and an ADMIN_RESOURCES entry.
  • Orchestrator: a human turn whose request leaves fastMode unset inherits the org default; an explicit per-turn fastMode (e.g. the web UI toggle) always wins. Triggered turns are unaffected (they already pass fastMode: false explicitly).
  • Admin UI card under Models & browsing with an on/off switch.
  • Tests covering default-off, persistence across instances, and cross-instance refresh.

@ReganBell
ReganBell force-pushed the fast-mode-default branch from d54de74 to 10133cf Compare July 30, 2026 22:38
@ReganBell
ReganBell merged commit e455cba into main Jul 30, 2026
15 checks passed
@ReganBell
ReganBell deleted the fast-mode-default branch July 30, 2026 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant