The shared engine behind the KY.AI dev-loop tools — the hub, supervisor, rolling log,
build tracker and MCP tool surface that ky-ai-ng,
ky-ai-dotnet, ky-ai-browser and
ky-ai-terminal build on.
Most users want one of those tools, not this library directly — install them with
dotnet tool install --global KY.AI.Ng / KY.AI.Net (plus the optional KY.AI.Browser console
add-on). This package exists so a new framework seam can reuse the same hub/supervisor machinery:
HubHost/Hub/HubTools— the control plane: one MCP server plus a registry of supervisors, addressed by name (incl. theshutdowntool).SupervisorHost/DevServer— runs a framework CLI, tees output, tracks build state, and auto-registers with the hub.RollingLog·BuildTracker·JobObject·Ansi— the build-aware log buffer (each line tagged with its build seq + classification, so it serves the raw view, a noise-freesummary, and since-seq / grep filters), the build-verdict logic (errors and warnings, structureddiagnostics, and change→build correlation), Windows Job Object process reaping, and ANSI stripping.HtmlInjector— the reversibleindex.htmlinject/uninject mechanism (POST /inject,ky-ai-ng-injectmarkers, self-heal) thatky-ai-browserdrives through the supervisor.InitCommand/ShutdownCommand/UpdateCommand— the shared CLI commands each exe dispatches:<tool> initwires the tool into a Claude Code workspace (merges its MCP server into the nearest.mcp.jsonand its command allow-list +enabledMcpjsonServersinto.claude/settings.local.json),<tool> shutdowntears down the hub and its supervisors, and<tool> updatestops running instances and runs the right package-manager update.
A framework tool supplies a BuildMatcher (mapping CLI output to build start/settle/error/warning,
and optionally parsing diagnostic lines into structured {severity, file, line, col, message}) and
its supervisor/hub configuration; the rest is shared here.
Loopback-only — nothing is exposed off the machine. See the project README for the full picture.