Skip to main content
Kernel CLI is the raw operating-system capability surface used by connector.json workflows. It can provide structured observation, semantic UI actions, machine telemetry, pixel fallbacks, and typed MCP tools without making the connector format itself an OS driver.

Read the canonical Kernel CLI docs

The canonical overview, installation path, cross-platform contract, and safety boundaries now live at /kernel-cli.

​
The Boundary

Each layer owns a different contract: Kernel CLI remains a standalone binary. A connector can call its raw commands, carry structured values between phases, and require a harness for writes.
  1. Run doctor or an equivalent health check on the target machine.
  2. Observe with snapshot, windows, ax-tree, or targets.
  3. Preserve snapshot_id and target_id between phases.
  4. Resolve the action with act --dry-run.
  5. Require the configured harness before a mutating phase.
  6. Act once and verify through a fresh read.
This flow is capability-first. OCR, screenshots, and coordinates remain available when the target has no useful semantic surface.

​
Connector Handles and MCP Element Tokens

connector.json can carry Kernel CLI result fields between steps, including target and geometry guards. It does not mint MCP element_token values. Reusable element_token values belong to the MCP computer_use facade. Use that facade when a client expects one portable capture/action loop; use raw Kernel CLI commands when the workflow needs the full OS surface.

​
Raw and Harnessed Execution

Direct Kernel CLI commands execute without an NIIA approval gate. For human-gated control, route the write through the NIIA control surface:
The human completes the OTP step. The connector does not grant itself control.

​
Continue Reading

Kernel CLI Overview

Product identity, capability surfaces, cross-platform behavior, and the raw versus harnessed boundary.

Kernel CLI Workflows

The observe, dry-run, act, verify, and NIIA-gated flows.

Kernel CLI Reference

Commands, permissions, platform behavior, operations, audit, and MCP.

connector.json

Return to the connector specification and orchestration model.