aik is the operator command for AIKernel.Tools. It uses Linux-style
subcommands:
aik <command> [arguments]The command surface is split between standard Core providers and external provider manifests.
dotnet tool install -g AIKernel.Tools.CLI --version 0.1.3
aik runtime ping
aik system info
aik system vfs --vfs-root .
aik capabilities invoke aikernel.vfs vfs.exists path=README.mdThese checks verify installation, runtime health, VFS access, and direct capability invocation.
dotnet tool install -g AIKernel.Tools.CLI --version 0.1.3These commands initialize AIKernel.Core standard providers before execution:
- MinimalRuntimeProvider
- SystemInfoProvider
- VfsProvider
- LocalExecutionProvider
- SkillProvider
Commands:
aik runtime ping
aik system info
aik system providers
aik system capabilities
aik system vfs --vfs-root .
aik system runtime
aik capabilities list
aik capabilities invoke aikernel.vfs vfs.exists path=README.md
aik exec run pipeline.json input.text=hello
aik skills list --root ./skills
aik skills show skill.example --root ./skills
aik skills invoke skill.example --root ./skills text=helloThe CLI prints deterministic key/value output for invocations and compact JSON for system snapshots. This makes the output suitable for shell scripts, ReplayLog comparison, and CI diagnostics.
The CLI separates command families by responsibility:
runtimeverifies the minimal runtime boundary.systemreads safe introspection metadata.capabilitiesoperates standard Core capability modules usingaik capabilities invoke <module> <operation> key=value.execsends local DSL pipelines to LocalExecutionProvider.skillsdiscovers and invokesSKILL.md-derived capabilities.providersloads external provider manifests and invokes their capability modules.gpulists and runs OS compute operations.run,ps,kill, andrestartmanage logical OS processes.logsreads logical process logs.schedulemanages scheduled OS commands.install providercopies built provider manifests and assemblies into a local provider directory.clock,vfs, andromremain direct inspector-oriented commands for operator diagnostics and compatibility workflows.nomosis a non-breaking alias for ROM / Canon inspection.chronosandreplayare non-breaking aliases for timeline inspection.
The command names intentionally follow Linux-style verbs and subcommands rather than UI-oriented language.
Concept aliases are additive only:
aik rom view
aik nomos view
aik clock timeline
aik chronos timeline
aik replay timelineExternal provider implementations are not part of Tools. They are installed or loaded from provider manifests:
aik install provider dynamic-pipeline
aik providers list --dir ./providers
aik providers capabilities --dir ./providers
aik providers invoke openai.chat chat.completion --dir ./providers prompt=helloThis keeps provider implementation logic in AIKernel.Providers while allowing operators to use a single command-line tool.
The CLI exposes a Linux-style OS surface for compute and process operation:
aik gpu list
aik gpu verify
aik gpu pending
aik gpu verify-native --provider dawn --package AIKernel.Dawn.Provider.0.1.3-dev1.nupkg
aik gpu verify-native --provider cuda13 --package AIKernel.Cuda13.0.Libtorch2.12.win-x64.0.1.3-dev1.nupkg
aik gpu verify-native --provider cuda13 --library native/build/win-x64/Release/libtorch_bridge.dll
aik gpu run vector-add --a a.bin --b b.bin
aik run sample
aik ps
aik kill <pid-or-name>
aik restart <pid-or-name>
aik logs sample
aik schedule add --every 1m "aik system info"aik gpu verify checks canonical GPU layouts, metadata, diagnostics, and
provider boundary rules. aik gpu pending prints the prioritized
remaining-work table for the canonical lane. aik gpu verify-native --provider dawn validates
DawnCore runtime assets plus native exports when a library is supplied.
aik gpu verify-native --provider cuda13 validates the package loader and
libtorch_bridge.dll runtime asset without requiring a LibTorch/CUDA runtime
load. When a Cuda13 library is supplied, the command loads
aikernel_cuda13_dispatch, sends the canonical 40-byte staged dispatch header,
and verifies NotInitialized / CommandSubmissionDisabled plus the
invalid-length fail-closed path.
When validating the built Dawn native fixture from this workspace, prefer the local-feed helper:
.\scripts\verify-dawn-native-fixture.ps1It generates ../artifacts/NuGet.canonical-local.v0.1.3-dev1.config, restores the
CLI against ../artifacts/local-nuget/v0.1.3-dev1, and then runs aik gpu verify-native --provider dawn --library <custom_bridge>. This avoids
accidentally restoring unpublished 0.1.3 packages from NuGet.org during local
canonical smoke checks.
For the full local canonical GPU lane, use:
.\scripts\verify-canonical-gpu-local-lane.ps1The lane chains Tools smoke tests, Wasm WebGPU package smoke, Dawn package and
fixture checks, Cuda13 package smoke, and the Cuda13 direct-library probe. The
Cuda13 direct-library probe remains dependency-aware and accepts the current
missing-dependent-module boundary unless -RequireCuda13LibraryLoad is set.
Use -RequireFreshCuda13NativeBridge for release lanes that must reject a
packaged libtorch_bridge.dll older than the native C++ bridge sources.
The lane also passes the generated canonical local NuGet config through Dawn/Cuda13
CLI build steps so unpublished 0.1.3-dev* dependencies resolve consistently.
For ad hoc commands before public 0.1.3 packages exist, generate a local
NuGet config and pass it explicitly:
.\scripts\new-canonical-local-nuget-config.ps1
dotnet restore src/AIKernel.CLI/AIKernel.CLI.csproj --configfile ..\artifacts\NuGet.canonical-local.v0.1.3-dev1.config -p:UseLocalPackageVersion=true -p:LocalPackageBuildNumber=1
dotnet run --no-restore --project src/AIKernel.CLI/AIKernel.CLI.csproj -p:UseLocalPackageVersion=true -p:LocalPackageBuildNumber=1 -- gpu pendingCommands that read through the standard VFS capability accept:
--vfs-root <path>The default is the current directory. The CLI registers a read-only local file
provider for this root path, so commands such as vfs.exists, vfs.read_file,
vfs.list, and vfs.metadata can run without external services.
Commands that load SKILL.md files accept:
--root <path>
--skill-root <path>The root defaults to skills or the AIKERNEL_SKILL_ROOT environment variable.
The SkillProvider discovers SKILL.md and Skill.MD files recursively and
registers them as capability modules. The preferred public spelling is
SKILL.md.
External providers are discovered from manifest files. A minimal manifest is:
{
"id": "openai.chat",
"name": "OpenAI Chat Provider",
"version": "0.1.3",
"assembly": "AIKernel.Providers.OpenAI.dll",
"capabilities": [
"chat.completion"
]
}CLI commands are fail-closed:
- unknown commands return a non-zero exit code
- unsupported capability operations return the provider error envelope
- missing provider manifests or missing
SKILL.mdroots do not silently create provider logic - external provider command failures are reported with the provider registry error message
The goal is to make operational failures visible and deterministic.
Commands return 0 on successful operation. They return non-zero when:
- the command or subcommand is unknown
- required arguments are missing
- provider manifests cannot be found or loaded
- no invoker is registered for a requested capability
- the invoked capability returns an error envelope
Output should remain parseable even on failure. Error text is printed explicitly so CI logs and replay diagnostics can capture the failing boundary.
Before publishing the CLI package:
- run
aik --helpthroughdotnet run - run
aik runtime ping - run
aik system info - run
aik capabilities list - run smoke tests under
AIKernel.Tools.Tests - verify that no command prints temporary stub text