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
A typed Ask that needs the Harness to look something up dies at twenty seconds.
"what's happening to NVDA stock today?" came back as The Harness reported an error: harness turn exceeded 20s; cancelled.
The Harness session takes the Completer timeout (src-tauri/src/harness.rs:407-408 → model::TIMEOUT, 20s). That number exists so an HTTP Completer hop can fall back to Static. A Harness turn that uses tools is not that hop — twenty seconds is not enough to search and answer.
Settings already says the same field budgets a Harness session/prompt (src-tauri/src/settings/form.rs HTTP limits disclosure). Blank still means 20s. Raising it by hand is a Development knob, not a default that lets an Ask finish.
Wanted
A Harness turn can run long enough to finish a tool-using Ask. Whether that is a higher default, a separate Harness budget, or no cap on the Ask path is a design choice — the 20s Completer number should not be the one that kills it.
Done when
The same Ask ("what's happening to NVDA stock today?", or any question that needs a web lookup) is not cancelled at 20s.
A hung Harness turn is still cancellable; this is not "wait forever."
Activity