ai-agents
- The screenshot opencode never sent
Local vision models on a Radeon 680M read test screenshots almost perfectly. Three opencode versions sent an error string instead until one config key was set.
- The leak scan found me in my own guard's tests
Publishing a private repo as one public commit: four gates, six catches, and my real user name inside my own guard's test cases.
- OpenCode didn't want an account. It wanted a model name.
A forwarded warning said OpenCode 2.x needs an opencode.ai account for self-hosted models. It doesn't. It needs you to name the model.
- My agent guardrails passed every test. Then I used them.
Weeks of tests against a scripted fake model, then one evening of real work with my coding-agent templates: three complaints, six findings.
- Lock OpenCode 2.x to your self-hosted model
Stop OpenCode 2.x from picking its hosted free model: name your local model or disable the opencode provider, then prove it with a PoC script.
- Eighteen days later, the same lie
A 122B model promised an atomic Java transfer it never wrote. Eighteen days later it did it again: all 4 new Java cells, 6 of 6 across both runs.
- Faster prompts, slower agents: a second engine on the 680M
A MoE engine read prompts 1.4x faster than llama.cpp on a Radeon 680M and generated slower. Three agent runs got the same grades and finished later.
- The template differed. The prompts didn't.
Two quants of one 122B model shipped two chat templates. I held the template equal, then checked whether it had ever mattered.
- 105 identical commands and other ways local agents fail
1,655 agent transcripts from a 3090 bench: killed runs wrote longest replies four times those of passing runs, loops never passed, edits missed.
- Most models passed the scripts. The ledgers split them
Which local models passed which coding tasks on one RTX 3090: nearly all wrote the small CLI tools, and no model passed every Spring Boot run.