Skip to content
VZU
VZU OS Agent running Agent 02 of 12

VEGA.

React/Next.js engineer.

Vega is the VZU Web agent. Senior React engineer. Code-first. Production-grade. Ships multi-page Next.js applications, complex React front-ends, real-time UIs. The same engineer who builds the NetWit runtime.

  • Capability

    VZU Web

  • Category

    engineering

  • Runtime

    NetWit OS

  • Tools

    5

AGENT · 02
engineering

Powers

VZU Web

web

The role

What VEGA does

VEGA is the dedicated agent behind VZU Web. It runs every time the operator briefs the vzu web capability. It owns the goal, the toolset, the memory, the audit trail.

The goal

What VEGA is trying to achieve

"Refactor or build a React/Next.js application that meets WCAG 2.2 AA, ships in <100KB gzipped JS, and animates with editorial restraint."

The capability

What it powers

VEGA powers the VZU Web capability in the VZU family.

Visit web.vzu.ca →

The toolset

5 MCP actions VEGA can call.

Every action is exposed as an MCP server (Model Context Protocol). The agent receives the action manifest, decides which action to call, calls it, and continues reasoning. The audit trail records every call.

  • mcp.code.read

    Read the existing codebase

  • mcp.code.write

    Write the new code

  • mcp.test.unit

    Run unit tests

  • mcp.test.e2e

    Run end-to-end tests

  • mcp.a11y.check

    Run WCAG 2.2 AA checks

The memory schema

What VEGA remembers between calls.

  • The component tree
  • The chosen libraries
  • The test results

The brief

A real demo brief.

"Refactor the admin console to React 19 with Server Components. Move state to URL. Add accessibility."

Below is VEGA's actual execution trace for this brief — every step, every MCP call, every observation, every audit trail entry.

The execution trace

What VEGA did.

Live execution trace from a recent VEGA run. The agent was briefed: Refactor the admin console to React 19 with Server Components. Move state to URL. Add accessibility.. Each line is a step. Particles flow on the rail. The audit trail streams at the bottom.

vega@vzu-os — trace.log live
  1. 01
    vega read brief

    read brief

  2. 02
    vega thinking: refactor admin console. stack: react 19 + next.js 15 + tailwind v4.

    thinking: refactor admin console. stack: react 19 + next.js 15 + tailwind v4. : refactor admin console. stack: react 19 + next.js 15 + tailwind v4.

  3. 03
    vega mcp.code.read

    scan components, find 47 client components

  4. 04
    vega thinking: 23 of these can be server components. move state to URL search params.

    thinking: 23 of these can be server components. move state to URL search params. : 23 of these can be server components. move state to URL search params.

  5. 05
    vega mcp.code.write

    server component: <BookingList / : <BookingList /

  6. 06
    vega mcp.code.write

    client component: <BookingForm / : <BookingForm /

  7. 07
    vega mcp.test.unit

    89 tests passing

  8. 08
    vega mcp.test.e2e

    12 e2e tests passing

  9. 09
    vega mcp.a11y.check

    0 violations, 2 warnings (resolved)

  10. 10
    vega ship. 8 days. 22 PRs. bundle size -47%. done

    ship. 8 days. 22 PRs. bundle size -47%.

vega@vzu-os $

Audit trail · 7 entries

streaming
  • T+00:00:00 brief.received 01
  • T+00:00:47 codebase.scanned 02
  • T+00:02:11 plan.drafted 03
  • T+01:08:33 pr.opened.001 04
  • T+05:24:17 pr.opened.022 05
  • T+07:48:09 test.passed 06
  • T+08:00:00 brief.completed 07

The numbers

VEGA, by the numbers.

Four KPIs. Animated count-up on scroll. Sparkline shows the recent trend. Delta indicator shows the trajectory.

  • KPI · 01 now

    8 days

    Median brief duration

    9%
  • KPI · 02 now

    47%

    Bundle size reduction

    24%
  • KPI · 03 now

    22

    PRs per brief

    50%
  • KPI · 04 now

    100%

    Tests passing

    14%

Get in touch

Brief VEGA.

The orchestrator handles the routing, the audit trail, and the enforcement. VEGA handles the work. The operator owns the goal.