HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Fast-Editor
Lynkr
JavaScript2025–2026
Fast-Editor / Lynkr

Lynkr

Streamline your workflow with Lynkr, a CLI tool that acts as an HTTP proxy for efficient code interactions using Claude Code CLI.

AI & Machine LearningDeveloper ToolsCommand LineWeb DevelopmentSelf-hostedNetworkingAutomation & Workflows
Explore on GitHubRead Hacker News discussions
2Distinct people
6Mentions
0Explicit recommenders
640GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Streamline your workflow with Lynkr, a CLI tool that acts as an HTTP proxy for efficient code interactions using Claude Code CLI.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day6 dated mentions

Observed mentions: 2025-12-20 23:46:16 UTC to 2026-01-19 06:31:30 UTC.

0122025-12-20 00:00:00 UTC to 2025-12-21 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 202025-12-21 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-22 00:00:00 UTC to 2025-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-23 00:00:00 UTC to 2025-12-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-24 00:00:00 UTC to 2025-12-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-12-25 00:00:00 UTC to 2025-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-26 00:00:00 UTC to 2025-12-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-27 00:00:00 UTC to 2025-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 00:00:00 UTC to 2025-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 00:00:00 UTC to 2025-12-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-01-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-02 00:00:00 UTC to 2026-01-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-03 00:00:00 UTC to 2026-01-04 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-01-04 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 42026-01-05 00:00:00 UTC to 2026-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-06 00:00:00 UTC to 2026-01-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-07 00:00:00 UTC to 2026-01-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-08 00:00:00 UTC to 2026-01-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-09 00:00:00 UTC to 2026-01-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-10 00:00:00 UTC to 2026-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-11 00:00:00 UTC to 2026-01-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-12 00:00:00 UTC to 2026-01-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-13 00:00:00 UTC to 2026-01-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-14 00:00:00 UTC to 2026-01-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-15 00:00:00 UTC to 2026-01-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-16 00:00:00 UTC to 2026-01-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-17 00:00:00 UTC to 2026-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-18 00:00:00 UTC to 2026-01-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-19 00:00:00 UTC to 2026-01-20 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJan 19

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 202025-12-20 00:00:00 UTC2025-12-21 00:00:00 UTC110
Dec 212025-12-21 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-23 00:00:00 UTC000
Dec 232025-12-23 00:00:00 UTC2025-12-24 00:00:00 UTC000
Dec 242025-12-24 00:00:00 UTC2025-12-25 00:00:00 UTC110
Dec 252025-12-25 00:00:00 UTC2025-12-26 00:00:00 UTC000
Dec 262025-12-26 00:00:00 UTC2025-12-27 00:00:00 UTC000
Dec 272025-12-27 00:00:00 UTC2025-12-28 00:00:00 UTC000
Dec 282025-12-28 00:00:00 UTC2025-12-29 00:00:00 UTC000
Dec 292025-12-29 00:00:00 UTC2025-12-30 00:00:00 UTC000
Dec 302025-12-30 00:00:00 UTC2025-12-31 00:00:00 UTC000
Dec 312025-12-31 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 12026-01-01 00:00:00 UTC2026-01-02 00:00:00 UTC000
Jan 22026-01-02 00:00:00 UTC2026-01-03 00:00:00 UTC000
Jan 32026-01-03 00:00:00 UTC2026-01-04 00:00:00 UTC211
Jan 42026-01-04 00:00:00 UTC2026-01-05 00:00:00 UTC000
Jan 52026-01-05 00:00:00 UTC2026-01-06 00:00:00 UTC000
Jan 62026-01-06 00:00:00 UTC2026-01-07 00:00:00 UTC000
Jan 72026-01-07 00:00:00 UTC2026-01-08 00:00:00 UTC000
Jan 82026-01-08 00:00:00 UTC2026-01-09 00:00:00 UTC000
Jan 92026-01-09 00:00:00 UTC2026-01-10 00:00:00 UTC000
Jan 102026-01-10 00:00:00 UTC2026-01-11 00:00:00 UTC000
Jan 112026-01-11 00:00:00 UTC2026-01-12 00:00:00 UTC000
Jan 122026-01-12 00:00:00 UTC2026-01-13 00:00:00 UTC000
Jan 132026-01-13 00:00:00 UTC2026-01-14 00:00:00 UTC000
Jan 142026-01-14 00:00:00 UTC2026-01-15 00:00:00 UTC000
Jan 152026-01-15 00:00:00 UTC2026-01-16 00:00:00 UTC000
Jan 162026-01-16 00:00:00 UTC2026-01-17 00:00:00 UTC000
Jan 172026-01-17 00:00:00 UTC2026-01-18 00:00:00 UTC000
Jan 182026-01-18 00:00:00 UTC2026-01-19 00:00:00 UTC000
Jan 192026-01-19 00:00:00 UTC2026-01-20 00:00:00 UTC211

What Hacker News says

6 sources
vishalveera·Jan 19, 2026
Hi HN, I built an open-source proxy called Lynkr that lets AI coding tools like Cursor, Cline, Continue.dev, Claude Code, and OpenCode run on any model backend instead of being locked to a single provider. The problem I ran into is that most modern AI coding tools are tightly coupled to a small set of hosted models. That makes it hard to control cost, run locally, use enterprise endpoints, or experiment with different models without changing tools or workflows. Lynkr sits between the client and the model and speaks both OpenAI-compatible and Claude-compatible APIs. From the client’s point of view, nothing changes — but you can route requests to local models (Ollama, llama.cpp), OpenRouter, or enterprise endpoints like Azure or Databricks. Architecture-wise, it’s a thin HTTP proxy that translates requests, supports streaming, tool calls, a
Read the rest
nd adds optional features like prompt caching, simple routing rules, and workspace indexing for coding workflows. One feature I’ve found especially useful is hierarchical routing: requests can be routed through a priority chain of models (for example, try a local model first, fall back to a stronger cloud model on failure or for large contexts, and finally to a premium model for complex tasks). This makes it possible to mix cost, latency, and quality policies without changing the client. A few concrete use cases that motivated this: Running Cursor or Continue fully on local models for privacy Routing cheap tasks to local models and harder tasks to stronger cloud models Using Claude Code CLI without sending code to Anthropic’s hosted backend This is early-stage and very much infra-focused. Setup is a single binary / npm install, and you point your tool’s base URL at Lynkr. Repo: https://github.com/Fast-Editor/Lynkr
In Run AI tools like Cursor,Claude Code, Codex on your own models
vishalveera·Jan 3, 2026
Quick share for anyone interested in LLM infrastructure: Hey folks! Sharing an open-source project that might be useful: Lynkr connects AI coding tools (like Claude Code) to multiple LLM providers with intelligent routing. Key features: - Route between multiple providers: Databricks, Azure Ai Foundry, OpenRouter, Ollama,llama.cpp, OpenAi - Cost optimization through hierarchical routing, heavy prompt caching - Production-ready: circuit breakers, load shedding, monitoring - It supports all the features offered by claude code like sub agents, skills , mcp , plugins etc unlike other proxies which only supports basic tool callings and chat completions. Great for: :white_check_mark: Reducing API costs as it supports hierarchical routing where you can route requstes to smaller local models and later switch to cloud LLMs automatically. :white_che
Read the rest
ck_mark: Using enterprise infrastructure (Azure) :white_check_mark: Local LLM experimentation ```bash npm install -g lynkr ``` GitHub: https://github.com/Fast-Editor/Lynkr (Apache 2.0) Would love to get your feedback on this one. Please drop a star on the repo if you found it helpful
In Lynkr – Multi-Provider LLM Proxy
vishalveera·Dec 20, 2025Submission

Show HN: Run Claude Code CLI with Azure&open source LLMs saving costs

Hi HN Claude Code CLI assumes the native Anthropic API, so it breaks or loses features when you try to run it with other LLMs on Databricks or Azure-hosted models or OpenRouter and other Ollama Models(no MCP, limited tools, streaming issues). I built Lynkr, an open-source compatibility proxy that lets Claude Code run unchanged on all the LLM's What it does: Emulates Anthropic’s protocol Claude Code expects Restores MCP server support It has hierarchical routing mechanism where you can configure multiples LLMs as a fallback to save costs Enables Git + repo intelligence tools Normalizes streaming/tool calling behavior Sub agents Implements Agentic context environment Framework and several other features Works without forking or modifying Claude Code
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.