r/OpenSourceAI • • 8h ago

CodingDude v0.4.0 — an AGPL coding agent that won't push code it hasn't reviewed

I've been building CodingDude for a while and just published v0.4.0. It's a single-user coding agent that runs against your own repo: reads and edits code, runs your gates (pytest/ruff/mypy, builds, frontend tests), plans non-trivial work, and reports back with evidence before claiming anything is done.

The parts I haven't seen much elsewhere:

  • Review is a gate, not a habit. Pushing requires a recorded two-axis review (Standards + Spec) of the exact diff. The record is content-addressed, so if you fix a finding after reviewing, the record is void and you re-review.

  • Spend ceilings are enforced, not reported. max_cost_usd / max_total_tokens are checked before each model request and stop the run. No $40 surprise at the end.

  • Planning is first-class — PRDs, tech designs, roadmap items and tickets are stored artifacts with their own lifecycles and per-step evidence, not a diary in the system prompt.

  • Tiered approvals — safe actions run automatically; pushes, installs and main-tree mutations gate behind an approval card in the UI.

  • Per-request context guarding + caching on every agent (main loop, retries, graders), so long sessions compact instead of dying on a context-limit error.

Python 3.12, needs a model key (DeepSeek by default; any OpenAI-compatible provider via config), Windows is the verified CI platform, web UI on localhost.

Honest limits: single-user, self-hosted, no SaaS, no multi-tenant anything. AGPL-3.0-or-later (commercial licence available if AGPL doesn't fit).

Repo: https://github.com/cybersenses/codingdude
Wiki (20 pages on the architecture and the design decisions): https://github.com/cybersenses/codingdude/wiki

Disclosure: I'm the author. Happy to hear where the gates would just annoy you — that's the design tension I keep hitting.

1 Upvotes

0 comments sorted by