Run from source
Clone the repo and bootstrap a local install inside the checkout.
git clone https://github.com/rebootix-research/viki-code.git && cd viki-code && python scripts/install.py --path .Rebootix Software Systems
The governed multi-agent coding system built to operate real repositories
Most coding tools stop at output. VIKI Code is built to continue from there, into planning, execution, validation, approvals, rollback, and governed change across real repositories.
Built for real repositories, governed execution, multi-agent task flow, and production-minded engineering, VIKI Code is Rebootix's coding system for teams that want more than autocomplete and more than chat.
Less assistant. More execution layer.
Built to inspect. Plan. Execute. Validate. Built to move from suggestion to infrastructure.
This is not passive AI. This is controlled software action.
Live repo operation
Planner - Builder - Verifier - Approval
Repo graph
Proof metrics
Controlled execution flow
Start VIKI Code
The current public proof set shows a real install path, real run path, and a built wheel flow documented directly from the repository.
Current public positioning
Live-tested. Repo-executing. Approval-aware. Built for serious software action.
Execution lane
Read the repo, map the targets, and establish operational context.
Break the work into controlled agent tasks with explicit scope.
Apply edits, surface diffs, and keep risky operations governed.
Return with checks, proof, and a clearer state than the one entered.
Installation surfaces
Three direct routes into the current public VIKI Code workflow.
Run from source
Clone the repo and bootstrap a local install inside the checkout.
git clone https://github.com/rebootix-research/viki-code.git && cd viki-code && python scripts/install.py --path .Run immediately after install
Launch the local API surface right after setup.
python scripts/install.py --path . --runBuilt artifact after build
Install from the documented 4.1.4 wheel artifact flow.
pip install dist/viki_code-4.1.4-py3-none-any.whlProduct positioning
VIKI Code is a live-tested coding system built for teams that need more than snippets and more than conversation. It is designed to operate across real codebases with structure, control, and proof.
Built to work inside real repositories, not outside them.
Approval-aware, rollback-capable, and validation-driven.
Designed to coordinate planning, implementation, review, validation, and execution.
Built around real workflows, not novelty demos.
Usable across CLI, API, IDE, and messaging-driven flows.
Strategic importance
The industry is crowded with coding interfaces that can talk about software. Far fewer can operate software systems with discipline. VIKI Code is built around that difference.
In serious engineering environments, the hard part is not producing text that looks like code. The hard part is entering a living repository, finding the right targets, making controlled edits, validating the outcome, and doing it without chaos.
That is the threshold VIKI Code is built to cross.
Threshold
VIKI Code is built for a new threshold in software execution, where the machine is no longer limited to suggestion and no longer confined to a passive window. It can inspect, plan, act, validate, and return with evidence.
That shift is powerful. It changes the role of the coding system from assistant to operator.
But power without control is noise. VIKI Code is built around governed execution, approvals, rollback, validation, and explicit task flow, because serious autonomy only matters when it can be trusted inside real repositories.
Serious autonomy is dangerous without control. VIKI Code is built to make it usable.
Execution stack
Works against actual codebases, not isolated text prompts.
Coordinates planning, implementation, review, validation, and execution across the same governed runtime.
Supports approvals, rollback, diff visibility, and controlled execution paths.
Built around tests, checks, and evidence-backed completion rather than pure output generation.
Available through CLI, API, VS Code integration, and messaging-connected workflows.
Developer surfaces
The same governed execution model is exposed across the developer surfaces that matter.
Direct operator control for repo intelligence, task submission, diff review, and status.
Local HTTP routes for orchestration, integrations, health, approvals, and run lifecycle visibility.
VS Code-oriented flows for repo-aware interaction, task submission, diff review, and session visibility.
Telegram and WhatsApp command surfaces for approvals, status, patches, logs, and operational handoff.
Operators
Evidence
VIKI Code has been exercised across live CLI and API task execution, generic-prompt workflows, benchmark runs, installed-wheel validation, and isolated execution paths. It is built and presented as a real product system, not a concept demo.
Local regression
59 passed
Broader live suite
9/9 passed
Public live benchmark
8/8 passed
Public offline benchmark
8/8 passed
Primary links
Follow the public evidence trail directly from the repository: source, proof, release notes, and benchmark records.
Rebootix
VIKI Code is a project of Rebootix Artificial Intelligence Research and Development.
Rebootix builds advanced AI systems, autonomous software infrastructure, and production-grade machine intelligence products focused on real-world execution. VIKI Code is part of that broader effort: practical AI systems designed to operate across actual developer workflows, governed environments, and serious engineering surfaces.
Closing directive
VIKI Code is built for that step. Not as a demo. Not as a trick. As infrastructure.