KVANTA22 AI-assisted game systems studio
Software / Systems

Tools forged in real production.

We build software when the work itself exposes a missing tool — then engineer it as a product. Coding infrastructure, Roblox systems, native utilities and local-first applications, all shaped by actual use rather than feature-page theory.

Explore the systems Build with us
Local-first Production-derived Systems-first Human-directed
KV22 // SOFTWARE FABRIC SIGNAL ONLINE
K22BUILD SYSTEM
CODEscoped agent ops PANELroblox interface MCOcombat fabric SENSORlocal health data TUNNELnative infrastructure INPUTfocused utility
07 PRODUCTS01 STUDIO∞ ITERATION
Software tools / 04

Focused tools. Built under pressure.

Four products, four distinct jobs. Each exists because we hit a real workflow that deserved a cleaner tool: agent coding, repetitive input, local glucose data and native tunnel operations.

Agent engineering

KV22 Code

ACTIVE BUILD

Give coding agents reach — without giving them the whole machine.

A local-first coding MCP built in Go for tightly scoped, administrator-controlled access to real development workspaces. Search, read, edit, inspect Git, run allowlisted checks and work across media while the host keeps hard boundaries around what an agent can touch.

Core capabilities
  • Workspace-scoped filesystem and Git access
  • Atomic edits, snapshot locking and durable operation receipts
  • Managed worktrees, indexing and optional language-server integration
  • Native media inspection plus a persistent Roblox Studio bridge
  • Local-first administration, audit trails and bounded commands
Input utility

Metatron Clicker

ACTIVE BUILD

A purpose-built hold-click utility for the repetitive input loops games actually create.

A focused auto-clicker created around Roblox workflows and the Fisch fishing loop, where reliable mouse press-and-hold behavior matters more than a giant automation suite. The product stays intentionally small: direct control, fast setup and a clear job to do.

Core capabilities
  • Designed around press-and-hold interaction
  • Built for Roblox and Fisch-style repetitive input loops
  • Focused utility surface instead of automation-suite overhead
  • Fast local operation with direct user control
Health technology

ZenSugar

IN DEVELOPMENT

Local-first continuous glucose data, designed as a native iPhone experience.

A native iOS continuous glucose monitor client being built first-class for AiDEX X / LinX sensors. ZenSugar focuses on direct Bluetooth communication, resilient background collection, gap recovery and readable history without making a cloud account a requirement for core monitoring.

Core capabilities
  • Direct local AiDEX X / LinX Bluetooth communication
  • Background collection, reconnect and sensor-history backfill
  • Lossless local history with deterministic de-duplication
  • Alerts, treatments, statistics and gap-aware history architecture
  • Sensor-neutral core designed for future widgets, watch and sync integrations

Development software. ZenSugar is not a validated medical device and must not be the sole basis for insulin dosing or emergency decisions.

macOS infrastructure

Cloudflared Monitor

ACTIVE BUILD

Run a local Cloudflare Tunnel like a visible native system, not a mystery process.

A lightweight native macOS menu-bar app for operating a local Cloudflare Tunnel without hiding the process behind a background daemon. Tunnel state, controls, safe config editing and live logs stay visible when you need them.

Core capabilities
  • Native menu-bar controls with connection state at a glance
  • Duplicate-process detection, startup and auto-connect controls
  • Config validation before replacement plus automatic backup
  • Real-time terminal-style logs with bounded file size
  • Universal Apple Silicon + Intel build with no telemetry
Roblox systems / 03

Production systems for Roblox.

MC-Outpost keeps producing infrastructure that should not stay trapped inside one game. These three systems are being hardened as reusable Roblox foundations: mass-combat architecture, production UI and reliable Studio control.

MCO FOUNDATION LIVE · EXPANDING
Roblox architecture

MCO Mass Combat Framework

The systems foundation growing out of MC-Outpost: a package-hosted Channel Fabric plus explicit domain Authorities for large, composable Roblox combat systems. Six playable-core Authorities are implemented in the current foundation; four additional domains are planned.

  • Channel Fabric package discovery, admission, routing and lifecycle
  • Six current Authorities: entity, relationship, combat, sensor, state and target intent
  • Contract-first package boundaries with deterministic verification gates
  • Place-neutral foundation designed for reusable game composition
6 / 10 authority domains
PK PRODUCTION-DERIVED
Roblox UI system

PanelKit

A self-contained Roblox panel framework extracted from production UI: draggable, resizable and foldable shells paired with a broad reusable widget library. Drop it into a project without pulling in the game that created it.

  • Roughly 30 reusable widget builders
  • Draggable, resizable, foldable panel shell and modal handling
  • Seven-color palette plus 77 individually addressable style tokens
  • Side navigation, schema forms, split panes and parameter help
  • Zero external runtime dependencies; drag-and-drop or Rojo install
77 style tokens
MCP PRODUCTION TOOLING
Roblox Studio tooling

KV22 Roblox Studio MCP

A dependency-free CLI bridge we built around Roblox Studio’s MCP server. Instead of trusting a long-lived editor connection, it spawns a fresh StudioMCP bridge per invocation, enumerates the live toolset and targets the intended Studio instance explicitly.

  • Fresh StudioMCP bridge per call avoids stale zero-tool editor sessions
  • Luau execution across Edit, Client and Server DataModels
  • Instance inspection/search, console output, screenshots and Play control
  • Dynamic live tool and schema enumeration; current sandbox exposes 26 tools
  • Safe multi-Studio targeting that refuses ambiguous calls; Python standard library only
26 current Studio tools
Engineering doctrine

Build the missing layer.
Keep the control.

Different products, same operating philosophy: constrain complexity, preserve ownership and make the system observable enough to trust.

01Local before cloud

Core workflows should keep working without unnecessary remote dependencies.

02Boundaries are features

Scopes, contracts and explicit ownership make powerful systems safer to evolve.

03Production is the test

We prefer capabilities proven by real work over long speculative feature lists.

04Fast is architectural

Lightweight interfaces, bounded work and deliberate dependencies keep tools responsive.

Open channel

Need a system that does not exist yet?

That is usually how these started.

Talk to Kvanta22