Why I’d Put Lynkr Between Goose and My Model Stack
Open-source coding agents are getting a lot more useful, and Goose is one of the clearest examples of that shift.
Goose is an open-source AI agent that goes beyond autocomplete. It can inspect code, execute tasks, edit files, and work through real development loops that look much closer to install → execute → edit → test than traditional code assistance.
That also means Goose creates the exact kind of workload where the model layer starts to matter a lot.
Once an agent is reading files, retrying commands, generating code, reasoning across context, and iterating through multi-step tasks, the cost and reliability of your model setup stops being a background detail. It becomes part of the product experience.
That’s why I think the cleaner architecture is:
Goose
↓
Lynkr
↓
OpenAI / Anthropic / Ollama / OpenRouter / Bedrock / Azure
In other words: use Goose as the coding agent, and use Lynkr as the LLM gateway underneath it.
What Goose is
If you haven’t looked at it yet, Goose is an open-source, extensible AI agent built for more than just code suggestions. The project describes it as an agent that can install, execute, edit, and test with any LLM, which is exactly why it’s interesting.
That framing matters.
A lot of developer AI tooling still assumes the model is mostly there to answer questions or generate snippets. Goose is part of the newer wave where the model is expected to participate in a real workflow. That means the token pattern changes too:
- more repeated context
- more tool-style back and forth
- more retries
- more multi-step reasoning
- more chances to waste expensive model calls on easy tasks
That’s where a gateway helps.
What Lynkr does in this setup
Lynkr is an open-source LLM gateway. Instead of wiring Goose directly to a single provider, you point Goose at Lynkr and let Lynkr handle the model layer underneath.
That gives you one control point for:
- provider switching
- local + cloud model setups
- fallback handling
- routing
- caching
- cleaner long-term infrastructure
Goose stays focused on the agent workflow. Lynkr stays focused on how requests should reach the right model.
Why this matters for coding agents specifically
If you only make occasional direct API calls, model choice is simple.
If you use an agent heavily, it isn’t.
A Goose session can easily include:
- reading repo context
- planning a change
- generating code
- fixing an error
- retrying with more context
- running another step
- revisiting earlier files
That is not one request. It is a chain of requests with different complexity levels.
Some of those steps can run on a cheaper or local model. Some need a stronger cloud model. Some repeat enough context that caching matters. Some need a fallback path because a provider slows down or fails mid-session.
Without a gateway, that logic ends up scattered or simply ignored.
With a gateway, you can manage it in one place.
Basic idea: point Goose at Lynkr instead of a raw provider
The exact Goose setup may vary depending on how you run it, but the architecture is straightforward:
- Goose talks to one model endpoint
- that endpoint is Lynkr
- Lynkr forwards to the real provider you want underneath
A typical environment setup looks like this:
export OPENAI_API_BASE=http://localhost:3000/v1
export OPENAI_API_KEY=dummy
Then run Goose normally:
goose
Or for a direct task:
goose run "Review this repo and suggest 3 refactors"
In this flow, Goose thinks it’s talking to its configured LLM endpoint. Lynkr handles what happens next.
Example 1: Run Goose on a local model through Lynkr
Let’s say you want Goose to use a local coding model first.
A simple Lynkr config might look like this:
providers:
- name: local-coder
type: ollama
model: qwen2.5-coder:14b
routing:
default: local-coder
Then:
export OPENAI_API_BASE=http://localhost:3000/v1
export OPENAI_API_KEY=dummy
goose run "Explain this repository structure and identify dead code"
Why do this instead of connecting Goose directly to Ollama?
Because once Goose is pointed at Lynkr, you can change the backend later without changing the Goose-side integration.
That means you can start local, then later:
- switch to a better coding model
- add a cloud fallback
- route specific workloads differently
- keep the same stable endpoint for Goose
Example 2: Local-first, cloud fallback
A more realistic setup is usually local-first with a stronger cloud fallback.
providers:
- name: local-fast
type: ollama
model: qwen2.5-coder:14b
- name: cloud-strong
type: anthropic
model: claude-sonnet-4
routing:
default: local-fast
fallback: cloud-strong
Then configure Goose to talk to Lynkr:
export ANTHROPIC_BASE_URL=http://localhost:3000
export ANTHROPIC_API_KEY=dummy
goose run "Debug why the integration tests are failing and propose a patch"
This gives you a much nicer operating model:
- cheap/local by default
- stronger cloud help when needed
- Goose workflow stays the same
Example 3: One Goose workflow, multiple providers behind it
One of the biggest advantages of putting a gateway under a coding agent is that your model preferences change all the time.
Sometimes you want:
- a fast model for lighter steps
- a stronger model for code generation
- a local model for private work
- a backup provider when your main one rate-limits
With Lynkr, you don’t need to keep reworking Goose every time you change that strategy.
Example:
providers:
- name: fast
type: openrouter
model: openai/gpt-4o-mini
- name: coder
type: anthropic
model: claude-sonnet-4
- name: local
type: ollama
model: qwen2.5-coder:14b
routing:
default: coder
fallback: fast
Goose still uses the same top-level environment variables:
export OPENAI_API_BASE=http://localhost:3000/v1
export OPENAI_API_KEY=dummy
That’s the part I like most about the gateway pattern: the agent stays stable while the model layer evolves underneath it.
Where Lynkr becomes especially useful
There are a few situations where this setup becomes much more valuable than direct provider wiring.
1. You want to avoid vendor lock-in
If Goose is wired straight to one provider, every change becomes a reconfiguration problem.
If Goose is wired to Lynkr, provider changes happen underneath the same gateway layer.
2. You want local + cloud flexibility
A lot of developers want a local-first workflow but still need access to stronger cloud models when tasks get harder.
That’s much cleaner when Goose talks to one gateway instead of multiple provider-specific setups.
3. You want better cost control
Agent workflows can burn tokens in places that don’t need premium models.
A gateway gives you a place to route easier work more cheaply.
4. You want a more future-proof stack
Coding agents are changing fast. Model providers are changing fast too.
A stable gateway layer gives you a cleaner architecture than coupling every tool directly to every provider.
A practical mental model
The easiest way to think about this is:
- Goose = behavior layer
- Lynkr = model control layer
Goose decides what work to do.
Lynkr decides where that work should go.
That separation gets more useful as your workflows get more agentic.
Final thoughts
Goose is part of a bigger shift in developer tools. We’re moving from AI assistants that mostly answer questions to coding agents that can actually work through tasks.
As that shift happens, the model layer matters more.
If you connect Goose directly to a provider, it works.
If you connect Goose to Lynkr, you get a cleaner long-term setup:
- one stable gateway
- easier provider switching
- local/cloud flexibility
- fallback support
- better control over how your coding agent uses models
That’s why I’d rather put Goose on top of an LLM gateway than wire it straight to a raw provider.
If you’re already experimenting with Goose, this is one of the simplest ways to make the setup more flexible without changing the agent workflow itself.
GitHub