Local machine
KCC owns terminal orchestration, layouts, worktrees, session health, clipboard support, and on-machine lane execution.
Ecosystem fit
KCC sits between local execution and the rest of the Koydo stack.
That is the point. The product is useful because it speaks repo reality, hosted coordination, and public launch language at the same time.
Hosted control plane
The control plane owns account state, approvals, audit, machine identity, sync, and the shared commercial layer around the product.
Chat ingress
Chat routes become front doors that can reach the local workstation capacity you explicitly register.
Distribution + product surface
npm, package-manager channels, GitHub releases, and the product site give KCC a coherent distribution surface for external teams.
Repo ecosystem awareness
KCC can map real multi-repo product environments from the local workstation, so teams can work across apps, services, and tooling without losing context.
Hosted coordination layer
Account validation, machine revocation, sync, approvals, and audit live in the control plane so the local CLI stays fast while shared administration stays centralized.
Chat-to-local execution
KCC turns a workstation into reachable capacity: teams choose which lanes are routable, the backend queues work, and the machine with the right context sends the reply.
Commercial distribution
The product can ship through npm, Homebrew, Scoop, Winget, and a dedicated product site without splitting the codebase into separate platform forks.
Built for multi-repo teams
KCC is designed for teams that ship across apps, services, and tooling at the same time.
KCC starts from the local machine and keeps enough repo context to make launches, support work, and governance useful across a broader engineering surface.
web app
mobile app
admin console
backend services
AI tooling
release pipeline
marketing site