I’ve been running deep research with agents for the past few weeks on one question: what is the most promising future for cheap, fully local AI-driven software engineering?
After weeks of deep-research agent runs, the most recent and promising stack for cheap, fully local AI-driven software engineering found by 5 agents was:
Qwen4 27B + CoDoc
Turns out that the answer was David and the rock.
-
Qwen4 27B (David). Quantized, it should fit on a single 24 GB consumer GPU. The coding capability at this size is now good enough for the bulk of day-to-day engineering work provided the agent has the right context.
-
CoDoc (the rock). This is a proposed standard where every software library ships AI-optimized documentation inside the package itself:
docs/README.mdas entry point,docs/index.mdas catalog, plain markdown throughout. Version-matched by construction, offline, deterministic. In the JavaScript ecosystemnpm installputs the docs on disk next to the code.
According to the research agents: the bottleneck for a 27B local model is not raw intelligence, it’s the context. A small model hallucinating a v5 API is a context problem, not a capability problem and CoDoc fixes the context for free.
The evidence in the white-paper points in the same direction:
- Vercel’s own agent evals on Next.js 16 APIs (absent from training data): 100% pass rate with bundled docs + an
AGENTS.mdpointer, vs 53% without. The on-demand “skill” variant maxed at 79% and was never even invoked in 56% of cases. - The unknown European IT company, Amadeus, claims that they have observed reduction in hallucinated APIs, the use of deprecated patterns and repeated correction cycles but they do not provide any rigorous evidence beyond these statements. They say that they intend to develop CoDocBench to address this gap.
Now the Goliath part. The big labs’ and hyperscalers’ moat was never the model: open weights are commoditizing fast. Their moat is the paid context layer: RAG pipelines, hosted doc intermediaries, MCP servers, enterprise knowledge add-ons, etc. According to the research agents: CoDoc collapses that entire layer into npm install or the equivalent in each ecosystem. A standard that makes context free, local, and version-pinned is an existential matter for anyone monetizing context scarcity.
And now the best part, the timing :) The AI bubble is popping as I type this. Goliath’s capital expenditure thesis requires inference to keep getting more expensive and cloud dependency to keep deepening. With David and his rock, a decent modern laptop doing your engineering agent’s job for electricity money is Goliath’s worst nightmare.
The standard itself comes from an unknown European IT company, not from any lab, which is exactly why I believe it adds to its credibility (despite its lack of first-hand evidence): it has no incentive to route your context through a metered API or sell you tokens, quite the contrary, it has all the incentives to make inference as cheap as possible.
I have read CoDoc’s white-paper and while it is far from perfect, I do mostly agree with the output of the research agents that picked up on Qwen4 27B + CoDoc as the most promising future for cheap, fully local AI-driven software engineering.
And you, do you think that it is game over for the AI Goliaths?
how does codoc compare to something like understand everything that builds a graph?
-
CoDoc (Co-packaged Documentation) is a standard advocating for colocating AI-optimized documentation next to the code installed for each software library used in your project.
-
Understand-Anything is a Claude Code plugin that maps your existing codebase into a knowledge graph.
They are complementary. Software libraries following CoDoc would supply additional files and directories for each dependency in your project enriching the output of the Understand Anything plugin.
I also understand that they solve different problems. CoDoc would allow an AI agent to operate in auto-pilot mode (with less AI slop) by having all the necessary context locally for all your project’s dependencies. CoDoc enables the AI agent.
Understand Anything maps your codebase to help you navigate and understand a complex codebase (it builds a JSON graph). Understand Anything enables the human software engineer.
-
Pure drivel.
docs/README.md as entry point
Wow how innovative.
The big labs’ and hyperscalers’ moat was never the model
Uhm, yes it was. Open weight models are nowhere near the capabilities of frontier models. I’m guessing you didn’t use a frontier model to generate this slop.
You called it “pure drivel” and then quoted the one line that’s a file-naming convention, not the argument… The moat in CoDoc is that the documentation ships inside the package, version-matched, offline, deterministic. Can you tell me what proportion of software libraries today ship complete AI-optimized documentation within the library’s artifact? I’ll wait.
And to your frontier-model guess, the models behind the research agents are: Opus 5.5 and Astra. So no, not slop.
As for “open weight models are nowhere near the capabilities of frontier models”: sure, on raw benchmark scores (but they always end up catching up). Vercel’s evals on Next.js 16 APIs (absent from training data) show 100% pass rate with bundled docs vs 53% without. As stated in the post, the bottleneck for a 27B local model isn’t raw intelligence, it’s context. CoDoc fixes the context for free. A 27B on your laptop with the right context can beat a frontier model that’s hallucinating your v5 API signatures.
Keep letting the Goliaths vacuum your code, your tokens, and your money. The fizzy orange drink is on them.
P.S. Post and comment 100% written by a human, in case you had any doubts :)