Operator infrastructure for AI-native teams

The operator OS for multi-agent engineering.

KCC launches local agent swarms, governs risky repo actions, and turns a developer workstation into routable execution capacity for the broader Koydo ecosystem.

Operator lanes
16

coded roles across architecture, QA, content, and ops

Execution surfaces
4

terminal, control plane, chat ingress, package channels

Repo family awareness
Koydo-wide

tracks sibling koydo-* repos plus backend surfaces

operator console
kcc run --workspace full --backend tmux
slots: 16 active lanes: green audit: streaming
repos: koydo-web, koydo-mobile, saas, koydo-anvil, koydo-maven
chat ingress: omniview / slack bridge ready
approval gate: merge pending for c1-arch

Launch

  • preset full
  • layout 8x2
  • fallback safe
  • backend auto

Govern

  • repo policy
  • approval gate
  • writer detection
  • handoff memory

Route

  • machine register
  • slot map
  • reply markers
  • chat return

Three jobs, one product

Run, govern, and route local AI work without turning your terminal into a liability.

Run local capacity like an operating system

Launch tiled role-based agent lanes, keep worktrees isolated, and recover sessions without burning another hour on terminal choreography.

  • tmux and Windows Terminal backends
  • saved layouts, presets, and workspace fallbacks
  • session continuity with health checks and reconnect paths

Govern risky actions before they become cleanup work

KCC layers repo-aware rules, approval paths, merge controls, and operator memory over day-to-day coding instead of after-the-fact process.

  • repo and task governance packs
  • controlled merge workflow
  • audit and approval surfaces for higher-risk actions

Route remote demand into local agent supply

Bridge Slack or Omniview-style chat ingress into local machine slots, then send structured replies back once the lane finishes the work.

  • slot registration and machine identity
  • reply-marker extraction from live panes
  • hosted sync, account, and control-plane hooks

Built for a real repo family

KCC is not a terminal skin. It is the operator layer over the Koydo ecosystem.

Repo discovery, control-plane coordination, chat ingress, and release packaging now line up with the same product surface you can actually sell and deploy.

koydo-webkoydo-mobilekoydo-adminsaaskoydo-anvilkoydo-mavenkoydo-marketing

Repo ecosystem awareness

KCC now discovers sibling koydo-* repos and `saas` directly from the local workstation, so the operator view matches the actual product family instead of a toy demo manifest.

Hosted coordination layer

Account validation, machine revocation, sync, approvals, and audit belong in the control plane so the CLI stays fast while the product becomes sellable.

Chat-to-local execution

KCC turns a workstation into reachable capacity: the operator chooses which slots are routable, the backend queues work, and local lanes answer from the machine that owns the context.

Commercial distribution

The product can ship through npm, Homebrew, Scoop, Winget, and a dedicated product site without splitting the codebase into separate platform forks.

Launch motion

Ready for internal rollout now, shaped for external production next.

  • 01Validate local workstation launch, merge, and reconnect flows.
  • 02Turn on hosted account, approval, and audit paths.
  • 03Deploy the product site and lock public pricing copy.
  • 04Open Pilot seats, then expand to Pro and Enterprise motion.

Pricing snapshot

$24per operator / month billed annually

$29 month-to-month

  • full local CLI and workspace orchestration
  • hosted account validation and synced state
  • chat bridge, handoff memory, and governed merges