The operator console for the Harness

The repository ships the carnelian binary: a real terminal surface for the daemon, tasks, skills, migrations, logs, and MAGIC. KRNL CLI is the brand language for how this control plane grows toward multi-workspace developer operations.

SHIPPING COMMAND SURFACE

Operate the system without a chat window

The alpha-complete CLI exposes fifteen command groups around the running Harness. Broader repository and service orchestration remains an in-development direction.

LIFECYCLE

Start, inspect, stop, migrate, and read logs from the local Carnelian daemon.

TASKS

Create governed work and follow execution through the same persistent task pipeline.

SKILLS

Refresh the active Skill Book as manifests and available worker capabilities change.

MAGIC

Authenticate providers, inspect status, sample entropy, and list the available provider waterfall.

CARNELIAN · OPERATOR CONSOLE

$ carnelian start
$ carnelian status
$ carnelian task create "prepare the release"
$ carnelian skills refresh
$ carnelian magic providers
$ carnelian magic sample

COMMAND TO OUTCOME

One terminal, the full governed pipeline

A command becomes durable work rather than a disposable prompt. It enters the same context, policy, worker, and ledger machinery used by every other interface.

Command

The operator states intent or requests a system operation.

Daemon

The local service resolves session and system state.

Policy

Capabilities and approvals govern execution.

Event stream

Progress and results return through observable events.

Karnelian's connected agent architecture from soul to persistent memory

IN DEVELOPMENT

The wider KRNL CLI vision

The next layer treats repositories, services, workspaces, and builds as one governed graph while retaining the Harness security model.

Cross-repository awareness without erasing boundaries
Service and dependency state visible to planning
Multi-step build operations with staged approvals
Same memory, policy, worker, and ledger foundation