AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AIZenn AI/MLPublished: Nov 15, 2026, 04:00 JST

locally-uncensored coding agent: only 14B fixes bug in test

Send on LINE
locally-uncensored coding agent: only 14B fixes bug in test

3 Key Points

  1. What happened

    In a test of PurpleDoubleD's locally-uncensored app (AGPL-3.0-only), a coding agent was told to fix a one-line bug; the 3B model read the files and ran the failing test but stopped without editing, the 7B model looped on a non-existent src/ folder until the Loop guard halted it, and only the 14B model fixed calc.py and passed the test.

  2. Why it matters

    The app's own mechanics—file reading, diff-based change proposals, approval-gated shell execution, and loop detection—worked correctly across all models, so the failures point to model capability rather than the app itself; for practical coding-agent use, users may need to choose models at the 14B level or above.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The locally-uncensored project, which gained over 200 stars in a day on GitHub Trending, aims to bundle chat, image generation, video generation, and a coding agent into one local desktop app. This test focused solely on the coding agent's ability to fix a simple bug, setting aside image and video generation which require ComfyUI and 6–12GB of VRAM. The app itself is built with Tauri (Rust+React) and can run in a browser-based development mode, which was used for this test.

The test environment included an AMD Ryzen 7 7700 CPU, 30GiB RAM, and an NVIDIA GeForce RTX 5060 Ti 16GB GPU. The app auto-detected an existing Ollama installation and listed available models. The onboarding recommended 9B-class abliterated models as "Agent-ready," hinting that the app's creators already recognized the need for larger models for agent tasks. The results confirmed this: the 3B model stopped after seeing the test fail, the 7B model got stuck looking for a non-existent src/ directory, and only the 14B model successfully edited the file and passed the test.

One notable observation was that in Ask mode, file edits are staged as "Pending" and not applied until approval, but the agent can proceed to run shell commands before approval. This caused the 14B model's first test run to fail because the edit hadn't been applied yet, leading to an extra round of editing and testing. The author suggests that waiting for edit approval before allowing shell execution would be more natural. Overall, the app's infrastructure—including diff-based staging, approval-gated shell execution, and loop guard—worked correctly, but the coding agent's success depended heavily on model capability, with 14B being the minimum for this simple task.

FAQ
What was the coding task given to the agent?
The agent was asked to fix a bug in calc.py where add(a, b) returned a - b instead of a + b, and then run test_calc.py to confirm the fix.
Did the app's features like loop guard work?
Yes, the Loop guard detected when the 7B model repeated the same tool sequence three times and halted the run, preventing endless token consumption.
What models were tested?
The models tested were qwen2.5-coder:3b-instruct-q4_K_M, qwen2.5:7b-instruct, and qwen2.5:14b-instruct, all run via Ollama.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGemtek back in operating profit in third quarter of 2026