Inspect and diagnose.
kingai version kingai status --json kingai doctor --json
Developer Platform · D5 Pre-Alpha
Developers
Build against what exists.
See the boundaries that still move.
KINGAI OS combines familiar Linux development with a governed local intelligence runtime. The public source already includes a CLI, local daemon services, policy/approval/task/memory/model foundations, build paths and release gates. Interfaces are still pre-alpha and may change.
Early interface preview · not a production screenshotUse source/status links below for current engineering truth.
CLI · current source
Start with commands that are actually documented.
The current developer CLI exposes system health, policy, approvals, memory, models, tasks and Desktop mode controls. These are pre-alpha interfaces, not a frozen public SDK contract.
Evaluate authority.
kingai policy check filesystem.read kingai approval list kingai approval request main filesystem.write ./project
Work with runtime primitives.
kingai memory list kingai task list kingai desktop show
CLI names and arguments can change before Beta/Stable. For the current canonical command set, use the public repository README and current source.
Runtime API surface
Local by default. No fake “cloud API” promise.
The current kingaid runtime uses a local Unix socket rather than exposing a management TCP listener by default. Current services include health/status, Agent Registry, capability-policy evaluation, Approval Broker, local Memory, Model Router, Task Graph and Audit.
Why that matters
Local peer identity can be tied to Unix credentials, while privileged decisions remain separate from ordinary client requests. The project is building an execution path where capability and owner approval matter before higher-risk actions.
Build & test
Reproduce the foundation from source.
The repository documents core checks and edition-specific image builds. Use current repository documentation as the source of truth for dependencies and release gates.
Validate the runtime.
make check make build
Build the PC edition path.
sudo bash scripts/build-rootfs.sh desktop amd64 dist sudo bash scripts/build-live-iso.sh desktop dist
Build the OCI development image.
docker build -f container/Dockerfile \ -t kingai-os:dev .
Documentation map
Go from product concept to engineering evidence.
Architecture
Runtime layers, governance direction, editions and system boundaries.
Status & release gates
Separate implemented and validated foundations from planned production-complete capability.
Security
Capability policy, approvals, local identity, audit and the constrained-execution direction.
Developer FAQ
Know what you are integrating with.
Is the developer API stable?
No. The current line is D5 Pre-Alpha. CLI and local runtime services are real engineering surfaces, but compatibility is not yet frozen for third-party production integrations.
Is there a hosted KINGAI OS REST API?
The current runtime management direction is local Unix-socket first. The website does not advertise a hosted REST API that the source does not currently guarantee.
Can I build KINGAI OS myself?
Yes. The public repository documents make check/make build and edition-specific build paths. Hardware and release validation still determine which artifacts are officially supported.
Can an agent simply request root access?
That is specifically what the governance direction is intended to avoid. The current runtime separates capability policy and owner approvals; the final constrained privileged Execution Broker remains an active development milestone.
KINGAI Developers
Follow the source, not a slide deck.
Inspect current code and status, then join Early Access if you want future Desktop and developer-platform testing invitations.
Developer surfaces remain pre-alpha and can change as security, execution and release gates mature.