TriForce
AI Control Plane
One backend for AILinux 26.04, ai-coder, Nova and MCP-enabled workflows. TriForce connects authentication, model routing, provider fallback, system tools and federation without tying the platform to a single AI vendor.
$ curl https://api.ailinux.me/health {"ok":true,"status":"ok"} $ curl https://api.ailinux.me/v1/client/models # models available for the current access tier $ curl https://api.ailinux.me/openapi.json # machine-readable TriForce API schema $ AILinux → ai-coder → TriForce → model/tool provider
Backend
Client API
Tool Layer
Routing
AI is replaceable. The platform stays yours.
TriForce sits between AILinux clients and the intelligence/tool layer. Models can change, providers can fail, quotas can run out — the platform keeps a stable API and can route work to another configured path.
Model routing & fallback
Expose configured chat-capable models through one client API, track provider availability and recover from unusable routes instead of hard-wiring the system to one vendor.
MCP tool execution
Connect agents to code, files, Git, diagnostics, services, containers, search, federation and other operational tools through a controlled tool layer.
AILinux client platform
The same backend powers ai-coder, native AILinux clients and browser-facing Nova workflows, keeping authentication and model access consistent across interfaces.
Federation & infrastructure
TriForce can coordinate across the AILinux server, workstation and connected nodes while keeping health, logs and operations visible through one control plane.
AILinux 26.04
The operating-system layer: local files, packages, services, containers and desktop execution.
Platform overview →ai-coder 0.9.5
The coding and DevOps agent: plans work, calls tools, changes the system and verifies results.
ai-coder →Nova
The user-facing AI environment connected to the same TriForce model and service infrastructure.
Open Nova →