Stream timeout

[mserrano11]

Right now, I have access to DS4 Pro running on a Mac Studio. The problem is that it is slow, and an application default 300 second timeout is triggered, for some prompts, and Codewhale closes the connection accordingly.

I suggest having a configuration option, available through /config , that might allow a user to select larger timeouts, so that more servers have enough time to answer back.

This will enable Codewhale to be used with locally served Deekseek implementations.

[Hmbown]

Fixed in #2778 (3ca89255 merge, harvest commit e5fe46d): CodeWhale now supports [tui].stream_chunk_timeout_secs and /config stream_chunk_timeout_secs <seconds> for slow local/OpenAI-compatible servers. The configured value updates the live session and is used by both the outer streamed-turn timeout and the inner SSE byte-stream timeout; 0 maps to the default 300s, values clamp to 1..=3600, and DEEPSEEK_STREAM_IDLE_TIMEOUT_SECS remains a fallback.

Verification passed stream_chunk_timeout, client_stream_idle_timeout_uses_tui_config, and config_view tests, plus fmt/diff/version/co-author checks. The broader #2762 integration PR is now green across Linux, macOS, Windows, lint, CodeQL, npm wrapper smoke, mobile smoke, version drift, and GitGuardian. Thanks @mserrano11 for the concrete slow-local-server report and @cyq1017 for the draft fix in #2507. Please retest on the next v0.9 build and reopen if a local server still stalls despite a larger configured value.