fix(session): increase ClaudeStartTimeout from 60s to 120s
Some checks failed
CI / Check for .beads changes (push) Has been skipped
CI / Check embedded formulas (push) Successful in 21s
CI / Test (push) Failing after 1m15s
CI / Lint (push) Successful in 19s
CI / Integration Tests (push) Successful in 1m2s
CI / Coverage Report (push) Has been skipped
Windows CI / Windows Build and Unit Tests (push) Has been cancelled
Some checks failed
CI / Check for .beads changes (push) Has been skipped
CI / Check embedded formulas (push) Successful in 21s
CI / Test (push) Failing after 1m15s
CI / Lint (push) Successful in 19s
CI / Integration Tests (push) Successful in 1m2s
CI / Coverage Report (push) Has been skipped
Windows CI / Windows Build and Unit Tests (push) Has been cancelled
Fixes intermittent 'timeout waiting for runtime prompt' errors that occur when Claude takes longer than 60s to start under load or on slower machines. Resolves: hq-j2wl Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -10,8 +10,8 @@ const (
|
||||
ShutdownNotifyDelay = 500 * time.Millisecond
|
||||
|
||||
// ClaudeStartTimeout is how long to wait for Claude to start in a session.
|
||||
// Increased to 60s because Claude can take 30s+ on slower machines.
|
||||
ClaudeStartTimeout = 60 * time.Second
|
||||
// Increased to 120s because Claude can take 60s+ on slower machines or under load.
|
||||
ClaudeStartTimeout = 120 * time.Second
|
||||
|
||||
// ShellReadyTimeout is how long to wait for shell prompt after command.
|
||||
ShellReadyTimeout = 5 * time.Second
|
||||
|
||||
Reference in New Issue
Block a user