Skip to content

docs: compare with router proxies instead of dismissing them - #24

Merged
AqueGen merged 2 commits into
mainfrom
docs/router-proxy-comparison
Aug 11, 2026
Merged

docs: compare with router proxies instead of dismissing them#24
AqueGen merged 2 commits into
mainfrom
docs/router-proxy-comparison

Conversation

@AqueGen

@AqueGen AqueGen commented Aug 10, 2026

Copy link
Copy Markdown
Owner

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 only claude-code-router.

Rewrites the section to give the actual distinction:

  • a proxy overrides a whole tier (MODEL_OPUS, MODEL_SONNET, MODEL_HAIKU), so substitution is per tier and never per task - it sees the requested tier, not the work
  • Claude Code asks for one tier per session plus haiku for background chores, so tier-level substitution has three buckets; deciding exploration is cheap and review is expensive is what subagent delegation adds
  • no proxy can keep you inside Anthropic, since the provider catalogs do not list it - the real trade is data egress, server tools that need the request forwarded intact (the advisor tool), and the cache-read economics routing depends on
  • the two compose: a proxy reaches Claude Code background traffic (quota probes, conversation titles, command-prefix detection) that never surfaces as a dispatch

Drops the ToS-risk claim in favour of concrete costs.

Docs only - no release, and release-please will not cut one for a docs: commit.

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.
@AqueGen
AqueGen merged commit f823f4e into main Aug 11, 2026
2 checks passed
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