local-llm
- The proxy said unloaded. The model was loading.
A context probe gave up on four models loading behind my LLM proxy: its status was a snapshot up to 30 s old. Then a 336 ms stream timed at 120 s.
- The model that only says RUN
A fake model drove six coding-agent harnesses through dangerous commands. One block I had credited to a deny rule came from print mode having nobody to ask.
- The first engine on the A9 was started to be stopped
v0.3.1 would refuse any engine start on the A9 until its agent was replaced. Then my proxy started its first engine there, for a benchmark to take away.
- The benchmark said it was waiting. Once.
My LLM proxy must never pause the A9's benchmark queue. It couldn't see the queue between jobs, while it waited behind the proxy, or mid-handover.
- The typo followed the tag; the failures didn't
Flint misspelled its run folder 495 times, only under run tags with a -fl token. In a renamed-tag A/B the typo moved and the scores didn't.
- To a coding agent, 503 means try again
What Claude Code, opencode and Node clients do with a self-hosted LLM endpoint's 503s and silences, and the status codes that stop the retry loops.
- Cutting a stream doesn't cancel the turn
A LAN proxy for two GPU boxes learned to switch llama.cpp engines. Cutting streams to switch faster failed: agent clients re-send the turn.
- "Terminating immediately" took 90 seconds
systemd and a wrapper's EXIT trap sent llama-server two SIGTERMs. Its Ctrl+C-twice exit() ran inside the signal handler and deadlocked in glibc.
- Three models wrote the same circuit-breaker bug
Four agent-written circuit breakers from three models: a request sent before the outage decides the half-open trial, and all 17 hidden core tests pass.
- Flint mistyped its path and blamed the tools
Flint typed one wrong token in its workspace path. OpenCode refused 81 calls without naming the path; the model blamed a tool glitch and called its code done.