You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(settings): Development Completer/Harness knobs (timeout help, auth-retry, MCP bin) #447
Sibling of #436. User-facing Completer/Harness choice stays on the Director tab. This issue is Development-tab (and env) knobs that should survive for testing without becoming product chrome.
Turn timeout already lives under Development → Completer limits (AI_BUDDY_DIRECTOR_TIMEOUT_SECS) and harness already reads dev_flags::director_timeout_secs().
Auth-retry (60s), spawn backoff (5s→5m), and attach floor max(timeout, 10s) are hardcoded in harness.rs.
AI_BUDDY_MCP_BIN is env / beside-exe only.
What to build
Help text on Completer timeout — state clearly it budgets both HTTP Completer and Harness session/prompt (and cancel on expiry).
Auth-retry interval — Development number field (default 60s); env override same ownership pattern as other Completer limits if practical.
AI_BUDDY_MCP_BIN override — Development path/text field for power users / CI (not Director).
Activity