Launching today

Zagens
Desktop agent harness for DeepSeek V4
4 followers
Desktop agent harness for DeepSeek V4
4 followers
Agents quit early — patches land, tests still red. Zagens harnesses DeepSeek V4 on Windows: phased runs, review loops, verify before done. • Phased work — checklist, auto-continue, gates before steps close • Review pipeline — explore, implement, review; loops on failure • One window — tree, terminal, diffs, turn-by-turn replay • Cost panel — tokens, cache hits, savings per session • Approvals, skills, MCP — you control risky scripts & tools Local-first. BYOK. Windows preview.







Hey Product Hunt 👋
I built Zagens because I kept hitting the same loop: the agent writes code confidently, I find a hallucinated function name three files deep, and suddenly I'm spending an hour auditing everything it touched. It didn't mean to break things — it just has no way to verify its own work.
The problem isn't model IQ. We dropped superhuman autocomplete into an engineering workflow with no code review, no CI, no "are we actually done?" — just tokens and on to the next turn.
So instead of waiting for a smarter model, I built the engineering layer around it — a Windows harness, not prettier chat bubbles:
• Multi-agent pipeline — explore (read-only), implement, review; failed review loops back automatically
• Verification gates — builds, tests, and grep weigh in before a step is marked done
• Long-session discipline — checklist, auto-continue, turn-by-turn replay so work doesn't quietly drift
I also merged Office (Excel, Word, PowerPoint, PDF) into the same app — I was tired of switching between AI and document tools.
Local-first preview · BYOK · keys stay on your device · built for DeepSeek V4 (OpenAI-compatible too). Not affiliated with DeepSeek Inc.
zagens.com · didclawapp@gmail.com
If you've wrestled with agents that sound confident but ship broken code — what verification patterns have you wired into your own workflow? Would love to hear it. 🙏