Skip to content

docs: correct proxy-routing.json schema description - #312

Open
dean0x wants to merge 1 commit into
mainfrom
docs/proxy-routing-schema
Open

docs: correct proxy-routing.json schema description#312
dean0x wants to merge 1 commit into
mainfrom
docs/proxy-routing-schema

Conversation

@dean0x

@dean0x dean0x commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Summary

The CLAUDE.md documentation incorrectly described ~/.devflow/proxy-routing.json as a bare {port} object with all unrecognised keys rejected. In reality, subswitch 0.2.0's config schema accepts five keys: port, logLevel, anthropic, providers, limits.

What's Documented vs. What's True

Before (incorrect):

  • "port only — bare {port} object"
  • "the 0.2.0 routing runtime rejects unrecognised keys"

After (correct):

  • Strict schema with five keys: port, logLevel, anthropic, providers, limits
  • Devflow writes port plus anthropic.connectTimeoutMs: 120000 (the subswitch#27 TTFB workaround)
  • Unrecognised keys — including legacy limits.connectTimeoutMs — are hard startup errors

Verification

This fix is based on a source audit of subswitch 0.2.0's config.ts schema validation and confirmation that the live relay successfully loads the exact configuration devflow generates. See dean0x/subswitch#42 for related upstream context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant