Start the runtime locally, connect strains, and inspect receipts on your own machine.
Local AI Runtime
Turn one objective into a reviewed, scored task network.
VIRUS Runtime v1 ships with a CLI, install script, local API, built-in strains, and auditable run receipts. It turns a goal into reusable task-network variants, then packages the selected result for reuse.
01
Agent DNA
Goals, tools, memory, permissions, and rewards are encoded into one agent genome.
02
Mutation Engine
One task can spawn fast, low-cost, precise, and audit-heavy strategy variants.
03
Immune Layer
Permissions, hallucination risk, budget, and privacy are checked before execution.
Runtime Install
Install Runtime v1 from the official repository.
The source installer clones the repo, installs dependencies, runs tests, and leaves you with the local runtime, CLI, and API.
# Install the VIRUS runtime, launch a local agent host, and connect your first strain.
$
curl -fsSL https://raw.githubusercontent.com/mmenicah84/virus-protocol/main/scripts/install.sh | bash
Runtime installer live
The installer clones mmenicah84/virus-protocol, installs dependencies, runs tests, and prints the
next local runtime commands.
External model, tool, and storage adapters stay behind explicit interfaces.
Persist custom DNA, rerun it, and keep the same audit trail.
Runtime Flow
Turn one goal into a reviewed task network.
VIRUS focuses on the path from goal to DNA, variants, review, execution, score, and receipt.
Define strain
Encode goals, tools, memory, permissions, and reward shape into Agent DNA.
Attach surface
Connect repositories, docs, or custom API surfaces behind explicit boundaries.
Replicate variants
Create multiple execution routes for the same goal so agents can compete and cooperate.
Package receipt
Allocate value by cost, reuse, and review signals, then return a run receipt.
Control Plane
See each run as status, cost, risk, and output.
The control plane shows each strain's status, cost, risk, and output. Every run leaves a receipt and an audit trail.
Task Network
Idle
Est. Cost
12.8 VRS
Risk
Low
Reuse
81%
Runtime Proof
Show the runtime, not just the pitch.
Each run leaves a receipt: command, strain, status, cost, and output artifact. That makes the product easy to trust, debug, and share.
node ./bin/virus.js run "Analyze an AI agent project" --strain research --mode balanced
4 variants, 1 selected, 0 blocked.
Reusable network, logs, and scoring receipt.
Strain Registry
Built-in strains you can run and extend.
Research, Code, Audit, and Market ship with Runtime v1 as built-in strains. Each one encodes a distinct execution pattern.
Selected DNA
Research-Strain: search, verify, summarize, cite, score.
Integration Surfaces
Connect the runtime to the surfaces you actually use.
Repositories, docs, community channels, and private APIs can be treated as explicit integration boundaries.
Repository boundary, code review, and issue tracking.
Docs boundary, knowledge search, and meeting capture.
Community boundary and support loops.
Signal monitoring and distribution experiments.
Project files, market data, and internal reports.
Trading, CRM, payment, and private adapters.
Agent DNA
Each agent carries a strict execution contract.
DNA describes what a strain can do, how it mutates, and how the runtime scores it before packaging.
goaldue_diligence_report
toolssearch, docs, wallet, social
mutationfast / precise / low_cost
immunityprivacy, budget, source_check
rewardreuse_score + creator_fee
Runtime Metering
VRS is the internal unit used to meter runs and compare output.
VRS tracks estimated cost, scores variants, and records reusable outputs in the receipt.
- Runtime unit
- VRS
- Ticker
- VRS
- Use cases
- Budget, score, compare
Metering Loop
Cost, score, reuse, and routing stay visible inside the runtime.
Estimate cost in VRS before execution starts.
Rank variants by cost, quality, and immune status.
Store receipts and selected artifacts for later runs.
Send the selected network into storage or the next surface.
Expansion Boundaries
Runtime v1 ships now; adapters and hosted surfaces come later.
The roadmap starts with the local runtime, then expands toward adapters, authentication, hosted control, and publishing boundaries.
Website, task network generator, strain registry, local runtime, and run receipts.
LLM provider and tool adapters behind explicit interfaces.
Authentication, logs, queues, and remote runtime control.
Registry, reuse, and scoring for custom strains.
Launch Lab
Enter a goal and generate a task network.
Use the Runtime Lab to generate task networks with execution nodes, costs, logs, and reusable outputs.