Skip to content

Commit 6a1a4f4

Browse files
typhon8claude
andcommitted
feat: make PROVIDER_TIMEOUT_MS configurable via environment variable
Fixes #1583 The hardcoded 180s timeout caused fallback chains to fail when upstream clients (e.g. OpenClaw) share the same timeout — both fire simultaneously and the client disconnects first, bypassing Manifest's fallback logic. Reading from PROVIDER_TIMEOUT_MS env var lets self-hosted users set a lower value so fallbacks can complete within the upstream timeout window. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 6d60e55 commit 6a1a4f4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

packages/backend/src/routing/proxy/provider-client.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ export interface ForwardResult {
2929
isChatGpt: boolean;
3030
}
3131

32-
const PROVIDER_TIMEOUT_MS = 180_000;
32+
const PROVIDER_TIMEOUT_MS = parseInt(process.env.PROVIDER_TIMEOUT_MS ?? '', 10) || 180_000;
3333

3434
/**
3535
* Strip vendor prefix from model name (e.g. "anthropic/claude-sonnet-4" → "claude-sonnet-4").

0 commit comments

Comments
 (0)