by rebootix | 2026-03-12 19:59:01+00:00
Title: Show HN: VIKI-Code – Your AI Coding Agent Is Lying to You

URL: https://github.com/rebootix-research/viki-code

Text:
Here's an uncomfortable truth:

Every AI coding tool you're using is fundamentally broken.

Copilot. Cursor. Claude Code. They all do the same thing: suggest code that you copy, paste, test, and debug yourself.

They don't execute. They don't validate. They don't take responsibility.

THE DANGEROUS PART:

You're trusting AI suggestions for production code without validation. No approval workflow. No rollback. No safety net.

One bad suggestion goes live. Production breaks. Users suffer. Reputation tanks.

This isn't hypothetical. It's happening now.

WHY THIS EXISTS:

We built VIKI-Code because we were angry. Angry that "AI coding assistants" don't assist — they dump code on you and walk away.

VIKI-Code doesn't suggest. It executes.

THE SWARM ARCHITECTURE:

VIKI uses a swarm of swarms — multiple specialized agent teams:

→ PLANNER SWARM: Maps your repo, tracks symbols, predicts impact, selects tests
→ IMPLEMENTER SWARM: Makes real code changes across files
→ VALIDATOR SWARM: Runs your actual tests before acceptance
→ REVIEWER SWARM: Security audit, performance check, quality gates

Each swarm has multiple agents. They validate each other. They produce evidence.

GOVERNED EXECUTION:

• Isolated worktrees — Changes never touch main until approved
• Approval workflow — You see the diff before anything commits
• Rollback paths — Reversible by default, always
• Live validation — Your tests run before acceptance
• Evidence artifacts — Full audit trail, redacted logs

This isn't "trust me bro" AI. This is governed autonomy.

THE PROOF:

We don't do marketing claims. We do tests:

59 local regression tests — passed
9/9 live validation on fresh repos — passed
8/8 public live benchmark — passed
7/7 generic CLI live wins — passed
WSL-isolated execution — validated

Real bugs fixed. Real refactors executed. Real migrations completed.

THE TRADEOFF:

VIKI is slower than single-agent baselines. Time-to-green is longer.

We chose safety over speed. Every change goes through: plan → implement → validate → review → approve → execute.

If you need raw speed, buy another tool. If you need production-safe execution, you found it.

WHO THIS THREATENS:

→ AI coding tools that only suggest (most of them)
→ Teams shipping unvalidated AI code to production
→ "Move fast and break things" culture
→ Ungoverned AI execution

WHO THIS IS FOR:

→ Platform teams who need AI inside repos (not chat)
→ Engineering teams in large repos/monorepos
→ Compliance-driven orgs (finance, healthcare, enterprise)
→ Teams that need approvals, rollback, proof
→ Anyone who ships production code and cares about not breaking it

THE REALITY CHECK:

AI coding isn't about suggestions anymore. It's about execution.

The question isn't "Can AI write code?" The question is "Can AI execute code safely in production?"

VIKI-Code answers yes.

TRY IT:

git clone https://github.com/rebootix-research/viki-code.git
cd viki-code
python scripts/install.py --path .
viki run "Fix the broken calculation and run the relevant tests" --path .

Two minutes. Real execution. You decide.

LINKS:

GitHub: https://github.com/rebootix-research/viki-code
Product: https://rebootix-research.com/viki-code
Proof Report: https://github.com/rebootix-research/viki-code/blob/main/PRO...

BUILT BY:

Rebootix AI (Dubai) — We build production-grade AI systems that execute, not suggest.

THE CHALLENGE:

Try VIKI-Code for a week. Then go back to your current AI coding tool.

You'll notice something: you miss having AI that actually executes.

Questions? Ask away. We built this to be challenged.