Lynkr

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

Runs with mockssource: GitHubhomepageJavaScriptApache-2.0commit 24f5c602fe68

JavaScript, Apache-2.0 licensed. The project labels itself: agents, ai, ai gateway, claude, claudecode, code assistant, code generation and cursor.

Lynkr runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Server starts, responds to health checks with 200, and 1555 unit/integration tests pass across routing, compression, memory, caching, rate-limiting, and telemetry modules with mock credentials.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
639
forks
76
open issues
5
watchers
6
size
57 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing Lynkr, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • better-sqlite3 optional native dependency not compiled for Node 18 (npm install skipped binary build)3 minutes
  • task-ledger test suite cascading failure: Promise resolution is still pending — t.unref() on setTimeout in Node 18 causes event loop to exit before timer fires3 minutes
  • Config requires DATABRICKS_API_BASE and DATABRICKS_API_KEY before starting the proxy or loading config modules2 minutes
  • jev-router.test.js classifyJev LRU test fails because evaluateJev requires TYPESAFE_API_KEY1 minute
  • jev-routing.test.js scoreIntent test fails because classifyJev requires TYPESAFE_API_KEY1 minute
  • tencentdb-launcher.test.js expects tencentdbMemory.enabled defaults to true but code defaults to false (TENCENTDB_MEMORY_ENABLED === 'true')1 minute
Install time
2 minutes
Cold machine to finish
31 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
node --test test/... (95 test files) returned # tests 1555, # pass 1555, # fail 0; curl localhost:8081/health returned 200
Model tokens used
351,478
Exact commit tested
24f5c602fe68
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

# todo 0
# duration_ms 284.524088
All verified. Let me compile the final result.
exec
/bin/sh -lc 'cd /work/repo && echo "=== Final test count ===" && LYNKR_KNN_DIR=/tmp/lynkr-test-knn …
 succeeded in 64784ms:
=== Final test count ===
# tests 1555
# pass 1555
# fail 0
tokens used
351,478

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 2 minutes, faster than the median of the 37 comparable projects Argusic has measured.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 38 agents projects Argusic has installed and timed, Lynkr was the 6th fastest to reach a running state, and 28 of 38 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

agentsaiai-gatewayclaudeclaudecodecode-assistantcode-generationcursordatabricksdeveloper-toolsllamacppllmllm-gatewayllm-proxyllm-routerllmopsmcpollamaprompt-cachingself-hosted

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Lynkr.svg)](https://argusic.com/subject/lynkr)

Questions

Does Lynkr run?
Lynkr runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test Lynkr?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 24f5c602fe68. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test Lynkr?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Lynkr take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does Lynkr need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Lynkr?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does Lynkr compare with the alternatives?
Of the 38 agents projects Argusic has installed and timed, Lynkr was the 6th fastest to reach a running state, and 28 of 38 reached one at all.
Where is the evidence for Lynkr?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion