docs: compare with router proxies instead of dismissing them - #24
Merged
Conversation
free-claude-code has made gateway routing the obvious thing to ask about, and the old paragraph answered it with a one-line brush-off. Name both projects and give the actual distinction: a proxy overrides a whole tier, so it substitutes per tier and never per task, because it sees the requested tier rather than the work. Spell out what leaving Anthropic costs - data egress, server tools that need the request forwarded intact, and the cache-read economics routing depends on - and state plainly that the two compose, since a proxy reaches background traffic that never surfaces as a dispatch. Drops the ToS-risk claim in favour of concrete costs.
Review round 1 caught the section generalising one project onto a whole category. free-claude-code does substitute a whole tier at a time and lists no Anthropic provider, but claude-code-router matches on request headers and bodies with rewrites, retries and ordered fallbacks, and speaks the Anthropic Messages protocol - so both "substitution is per tier, never per task" and "no proxy can keep you inside Anthropic" were false about a project the section names. Each claim now sits with the project it is true of, and the reader is told to check rather than assume. The argument that survives is narrower and actually holds: a gateway sees the requested tier and the shape of a request, never whether this errand is a throwaway grep or the review guarding a release, and Claude Code asks for one tier per session plus haiku for chores. The costs of leaving are named as costs rather than compliance risk - egress, server tools that need the request to reach Anthropic intact, and the cache-read rate most of the saving rests on - and the intro drops its ToS-gray-zones line for the same reason.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
free-claude-code(45k stars) has made gateway routing the first thing people ask about, and the old paragraph answered it with a one-line brush-off naming onlyclaude-code-router.Rewrites the section to give the actual distinction:
MODEL_OPUS,MODEL_SONNET,MODEL_HAIKU), so substitution is per tier and never per task - it sees the requested tier, not the workDrops the ToS-risk claim in favour of concrete costs.
Docs only - no release, and release-please will not cut one for a
docs:commit.