Skip to content

feat(settings): Development Completer/Harness knobs (timeout help, auth-retry, MCP bin) #447

Closed

Description

@omesser

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.

Context

After #433:

  • 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

  1. Help text on Completer timeout — state clearly it budgets both HTTP Completer and Harness session/prompt (and cancel on expiry).
  2. Auth-retry interval — Development number field (default 60s); env override same ownership pattern as other Completer limits if practical.
  3. AI_BUDDY_MCP_BIN override — Development path/text field for power users / CI (not Director).

Explicitly not in this issue

Acceptance

  • Timeout row help mentions Harness turns
  • Auth-retry configurable from Development (and respected by harness)
  • MCP bin override configurable from Development (and respected at attach)
  • No Director-tab clutter; no credential or always-approve controls

Related: #436, #433, #166.

— Cursor agent (Architect), on @omesser's behalf.

Activity

  1. added this to the V1 milestone on Sep 7, 2026
  2. moved this from Todo to In Progress in Fidgeton Sep 8, 2026
  3. moved this from In Progress to Done in Fidgeton Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions