A Reddit user pairs Ornith 1.5-9B with Claude Code task planning
A Reddit user published a briefing methodology for using Claude Code to write specifications and small task cards that a local, 8-bit Ornith 1.5-9B can execute. In the reported workflow, the local model handles commands, builds, job polling and Git work, while the stronger model verifies results before merge. The author reports a 75-commit merge across two repositories with all regression tests passing, but acknowledges that the model’s completion notes were sometimes incorrect.
The account offers a concrete division of labor in which Claude Code prepares small-model-executable plans and Ornith 1.5-9B performs token-intensive implementation work on local hardware.
I've been running Ornith 1.5-9B (8-bit) as a local coding agent on real engineering work. It can do the work, but only when the plan is written for a small model. I wrote down what I learned into a public file meant to be handed to a stronger planning model (I use Claude Code):
The split
- The stronger model writes the spec and a plan of small task cards, then verifies the result before merge.
- The local model does the long, mechanical middle: running commands, builds, polling jobs, git work. That's where most of the tokens go, and it runs on my own hardware.
What the file covers
- What the small model is good at, and what to expect (work more reliable than its reports; doesn't explore on its own; doesn't know when it's done; slows down at long context).
- How to brief it: exact files and line ranges, absolute paths, 1–3 line edits, exact function signatures, every rule written down, every step ending in a command with its exact expected output, explicit stop rules.
- How to run it: one task per fresh session, small context, the plan file as memory.
- Before anything lands: verify claims against git and logs, not the model's summary.
Results so far: a 75-commit merge across two repos with every regression test passing, done by the 9B. Its notes about what it did were wrong more than once; the plan's checks and a final verification caught every one.
Limitations: slower (most of a day vs about an hour for Claude alone on that phase), and you need hardware that runs a decent local model. The rules are harness-agnostic but were learned with one model; I'd like to hear how they hold up with others.