// the find
Fast-Editor/Lynkr
Streamline your workflow with Lynkr, a CLI tool that acts as an HTTP proxy for efficient code interactions using Claude Code CLI.
Lynkr is a Node.js HTTP proxy that sits between Claude Code, Cursor, or Codex and whatever model backend you point it at, from a local Ollama box to a paid API. It compresses large JSON tool results, serves cached answers for similar prompts, and picks a model tier per request based on how hard the request looks. It is aimed at people who want to spend their subscription or API budget only on the requests that need it.
- The streaming path is the hard part of a proxy, and it is handled explicitly. Upstream Anthropic SSE is piped through with backpressure, and OpenAI-format upstreams are reshaped in flight, including reassembling fragmented tool-call arguments into proper tool_use blocks. Each path has a kill switch.
- The benchmark can be run. benchmark-tier-routing.js drives Lynkr and LiteLLM against the same backends, and the README says plainly that the routing scenarios come from Lynkr's own regression suite. The home-field advantage is disclosed rather than hidden.
- Routing decisions are pinned per session using a content fingerprint, since clients like Claude Code send no session id. A guarded escape ladder for risk keywords, score drift, and context overflow moves a task to a stronger model only when it needs one.
- The headline numbers (84% JSON compression, 53% tool reduction, 171ms cache hits) come from one Apple Silicon Mac against free local backends. The cache figure is a single paraphrase pair. The README does not say how the semantic cache avoids serving a stale answer for a near-duplicate prompt that differs in one file path or identifier, which is the case that quietly returns the wrong fix.
- The repo ships build output and binaries alongside source: native/lynkr-native.node, a native/target tree full of Cargo fingerprints, and an ONNX router model under models/router. A proxy that sits in the path of every request and every API key is harder to audit when it carries an opaque prebuilt binary.
- The feature surface has grown past the core job. There is a kNN router, a bandit, a memory store, a dashboard with a pivot explorer, an optional Rust-built graphify dependency, and 14+ providers. Many features are one env var away, and the troubleshooting section lists warnings that appear on a fresh install, such as missing TIER_* config and FALLBACK_PROVIDER with no credentials. The fix for 'no response after N turns' is just a default change in 9.3.0.