docs(proxy): credit claude-code-router

README.md

@@ -69,6 +69,17 @@ eval "$(ccs proxy activate)"
 
 Guide: [OpenAI-Compatible Provider Routing](./docs/openai-compatible-providers.md)
 
+### Related Project: claude-code-router
+
+[claude-code-router](https://github.com/musistudio/claude-code-router) is an
+excellent standalone tool for routing Claude Code requests to OpenAI-compatible
+providers. CCS's local proxy and SSE transformation work was directly informed
+by CCR's transformer architecture.
+
+Use CCR when you want a standalone router without CCS profile management.
+Use CCS when you want the routing flow integrated with CCS profiles, runtime
+bridges, and the existing `ccs` command surface.
+
 Need the full setup path instead of the short version?
 
 | Need | Start here |

docs/openai-compatible-providers.md

@@ -11,6 +11,23 @@ This is useful for providers such as:
 - llama.cpp servers
 - OpenAI-compatible self-hosted gateways
 
+## Related Project: claude-code-router
+
+[claude-code-router](https://github.com/musistudio/claude-code-router) is the
+main external reference that informed this CCS work. Their Anthropic/OpenAI
+transformer design helped shape the routing approach here.
+
+When to use CCR:
+
+- you want a standalone router without CCS profile integration
+- you do not need CCS account/runtime management around the request flow
+
+When to use CCS:
+
+- you already use CCS API profiles or runtime bridges
+- you want the proxy flow available through `ccs <profile>` and `ccs proxy ...`
+- you want the routing behavior documented and tested inside the CCS workflow
+
 ## What CCS Does
 
 When you launch a compatible settings profile with the Claude target, CCS now: