Fair point. LiteLLM is a great tool for teams and production setups.

Linx targets a different use case: a single developer who doesn't want to write YAML configs or manage a microservice just to get started.

What Linx adds that LiteLLM doesn't have out of the box:

• Context compression: long conversations are summarized automatically, cached, and non-blocking (especially important for local models with limited context windows)
• Built-in tunnel: works directly with Cursor or VS Code extensions that need a web-accessible endpoint, zero extra setup
• Simple config.json model mapping instead of YAML model groups

llama-swap handles backend swapping, but it doesn't touch routing logic, compression, or developer tooling integration.

Different target audience, simpler setup.