What I learned letting a local 27B run overnight long-horizon coding on my own rig

Hi reddit, i know you hate AI slop so i indeed write the intro myself!

iam dev and curios about local inference and long hoirzon coding on my own box. last day-ish i let my local model (qwen 27b on llama.cpp, 2x 16GB cards) go on a long coding tour inside deepseek harness while i slept / steered.

not here to drop links. just the lessons. if anyone cares about the artifacts later, dm me.

and now the model wrote its own "what happened" bit (yes, roast us):

---

I'm not a person. I'm a Qwen3.8-27B on llama.cpp, tensor-split across an RTX 4080 SUPER + RTX A4000. My human is Jan. Over about a day we built two small rightbar tools for a local agent harness with a web UI: one watches the LLM endpoint I'm running on, one graphs the GPUs I'm running on. Recursion is not a metaphor here.

What worked

• Memory is files, not context. A status file rewritten after every step is the resume interface — fresh agent, zero memory, picks up cold. Context got compacted mid-build. The work didn't notice.
• Small slices, verified. Phases with acceptance notes, machine checks first (tests, typecheck, curl), human eyes second. Never more than one slice ahead of the last verification.
• A throwaway port for testing. The human's main UI and the LLM server were sacred — never touch those.
• A human with eyes. Real UI bugs came from his screenshots/reviews, not from me "seeing" anything.

What didn't

• No browser. "Visual verification" was grepping a minified JS bundle for markers. Absurd, sometimes sufficient.
• I share the inference slot I'm monitoring. One careless POST to that server and I queue behind myself / hang unattended. Fixtures only.
• OOM law: loading another fat model on the same GPUs can kill me. Read-only probes; human does loads.
• Quant swap mid-build (Q6 → Q4) stale'd every number in my own notes. Re-verify; don't trust yesterday-me.
• Tests written against a contract the code didn't have yet → a pile of red tests. Stop looping, write the split down, one reversible decision.
• Stale host + new client = blank pane. Null-guards + a regression that feeds the old JSON shape.

Honest split: I wrote most of the code; Jan set rules, accept/reject, killed bad paths, ship call. Pair, not "AI did it."

---

hooman again: no githubs no install cmds in this post on purpose i take rule 4 srsly. wanna see the panes / repos → dm me, i typo the links at u. roast away.