Comment by brainless

18 hours ago

I have been building a coding agent for small and even tiny LLMs, local inference. I experiment with Qwen 3.5 0.8B but that is too tiny. 4B is a better one for most of my needs. I mix with 9B and then up to 20B models (not on my computer).

It builds on an opinionated tech stack - Rust (Actix Web, Diesel, SQLite) and Typescript (Solid, DaisyUI). There are multiple agents which play roles like PO, PM, Architect, Rust Engineer, Typescript Engineer and so on.

The idea is to go from user prompts to Epics/Tasks - PO/PM do this. Then to go from Tasks to YAML or similar syntax (I have not figured this out yet) and break into Rust and Typescript code dependencies.

I am focusing on the Rust side: how can small models write Model, Controller, Router, User/Permission and custom business logic in helper functions (called from Controller or BackgroundTask). Building a set of types to express business logic, for example in https://github.com/brainless/nocodo/blob/feature/praxis_agen...

Then I will use tree-sitter to build a graph of which business logic (in the helper functions) correspond with which provenance (source of truth given by user).

There is no tool calling for most of the agents, no MCP, no multi-turn chats. Most of the code writing agents one-shot the response with a lot of code reference in their prompts.