A developer building Xencode, a Rust terminal coding agent running local models via Ollama and llama.cpp, reports the harness — not the model — became the main engineering challenge. Failure modes like repeated tool calls, bloated context, and unwinding broken sessions pushed logic into the agent runtime. The post invites comparison with others running coding agents on local models.
A developer spent 8 months, 883 commits, and billions of tokens building a coding-agent harness that treats the LLM as a replaceable worker, with the system owning planning, state, permissions, verification, and orchestration. The harness verified claimed task completion instead of trusting the model, but kept accumulating features and was ultimately abandoned.
A developer spent 8 months, 883 commits, and billions of tokens building a coding-agent harness that treats the LLM as a replaceable worker, with the system owning planning, state, permissions, verification, and orchestration. The harness verified claimed task completion instead of trusting the model, but kept accumulating features and was ultimately abandoned.
A developer building an agent runtime in Rust opened a discussion on how to divide responsibility between the model and the harness. The core loop is straightforward, but failure cases — repeated tool calls, partial failures, oversized context, rollback, restarts, and premature completion claims — force reliability logic out of the model. The post asks practitioners which responsibilities they eventually moved into the harness and which should stay model-driven.
A developer building an agent runtime in Rust opened a discussion on how to divide responsibility between the model and the harness. The core loop is straightforward, but failure cases — repeated tool calls, partial failures, oversized context, rollback, restarts, and premature completion claims — force reliability logic out of the model. The post asks practitioners which responsibilities they eventually moved into the harness and which should stay model-driven.
Ollama published v0.34.1, a patch release updating its MLX runner and llama.cpp backends. Changes focus on memory handling: the mlxrunner now evicts prefix cache snapshots and waits for evicted runners and free system memory before loading the next model. The release also raises the token repeat limit to 100 and fixes a ChatGPT model selector spacing bug in the app.
Ollama published v0.34.1, a patch release updating its MLX runner and llama.cpp backends. Changes focus on memory handling: the mlxrunner now evicts prefix cache snapshots and waits for evicted runners and free system memory before loading the next model. The release also raises the token repeat limit to 100 and fixes a ChatGPT model selector spacing bug in the app.
LoopTroop is a local, open-source GUI app that acts as an orchestration layer for AI coding agents, addressing context rot during long vibe-coding sessions. It uses an LLM council planning approach and loops to maintain context, helping developers working on complex, long-running tickets.
LoopTroop is a local, open-source GUI app that acts as an orchestration layer for AI coding agents, addressing context rot during long vibe-coding sessions. It uses an LLM council planning approach and loops to maintain context, helping developers working on complex, long-running tickets.
A developer running Ollama on an M4 Pro Mac with 48 GB unified memory finds direct inference works fine, but the same model fails when used through coding agents. Claude Code with Qwen3.8 completes tasks accurately, while Codex with Qwen3.8 hangs and shows catalog warnings.
A developer running Ollama on an M4 Pro Mac with 48 GB unified memory finds direct inference works fine, but the same model fails when used through coding agents. Claude Code with Qwen3.8 completes tasks accurately, while Codex with Qwen3.8 hangs and shows catalog warnings.