Two users
A person and an agent. Same device, separate keys.
Both are real users of the system. Each has its own identity, its own permissions and its own lines in the log. You can always see what the agent did, and stop it.
Agentic OS · Linux kernel · Pure Rust above it
The operating system for two.
You and your agent share one small device. QingOS gives the agent hands — and keeps every permission, every confirmation and every log line with you.
● qinit● qing● qaudio— the whole machine after boot
3.2 MB kernel · 3 processes · Rust userspace · Wasm apps · no syscalls · Physical-key confirm · Signed A/B updates · No shell · no desktop · no distro
Each dot is a process. Grey: a typical Linux system after boot, for scale. Lit: QingOS.
01 · Nothing else runs
Hundreds of processes.
Or three.
A Linux distribution starts hundreds of programs before you touch it. QingOS keeps only the kernel, and writes everything above it in Rust. Fewer parts to break, to patch, to attack and to wait for.
3.2 MB
kernel, from allnoconfig
~1 s
power on to first light (QEMU)
~33 MB
runtime memory, apps included
0
shells on a shipped device
02 · Why QingOS
Built for agents.
Answerable to people.
Physical key
A button the agent can’t press.
Pay, send, unlock: each one waits for your finger on a real key. Saying “yes” is not enough.
Wasm apps
Apps can’t make system calls.
Each app is a wasm module with a manifest. It gets only what the runtime hands it, and declares the risk of every action.
Local power
Brain in the cloud. Power at home.
The model runs remotely. Permissions and the log never leave the device. Private data is replaced before a request goes out.
No model in the loop
Safe when the model isn’t there.
The guard calls no model. If the network or the model goes down, permissions and local actions keep working.
Many bodies
One system. Screens, robots, handhelds.
A machine file says what the hardware has. QingOS draws and runs only that: no screen, no screen code; no motors, no motor code.
03 · The guard
The agent asks.
The guard decides.
Every action the agent wants goes through one door. The guard does not try to read intent. It reads one thing: how much this action can hurt.
Tier 1 · Local
It just does it.
Set a timer. Change the light. Easy to undo, so no question. The light ring blinks once.
guard → run → log
Tier 2 · Remote
It asks once.
Look up a flight. Write a draft. The first time, you choose: A for this time, B for always. You can take it back any time.
guard → ask → remember → log
Tier 3 · Irreversible
You press the key.
Every time.
Pay. Send. Unlock. A spoken “yes” does not count. No standing permission exists. If nobody presses, nothing happens.
guard → wait for key → log who pressed
One door. The agent cannot reach the network, files or hardware except through the guard.
One line per action. Each allowed action is written to a log on the device and kept for 30 days.
Your call, always. Standing permissions are yours to give and to take back.
04 · Inside
Linux at the bottom.
Ours above it.
We keep the kernel for its drivers, process isolation and fast start. Init, network, Wi‑Fi security, audio, the screen and updates are our own Rust.
facesscreen · voice · light ring · LAN console
appswasm, isolated inside the runtime
runtimemind→guard→apps
baseqinit · qnet (DHCP, DNS, SNTP, WPA2) · audio · A/B updates
linux kernelmainline · only the drivers in use
05 · Devices
Already running on
four bodies.
From an 8-inch screen on your desk to a duck that walks on 15 servos. Same system, same guard, same apps model.
Every day
Desk screen
Arduino UNO Q with an 8-inch portrait touch screen. Boots into QingOS and updates over Wi‑Fi.
Product
Family display
Photos and moments from the people you love, on a screen at home. With its own server and iOS app.
In simulation · hardware arriving
VibeDuck
A two-legged duck on 15 servos. It walks, skates, looks around and sings in a round. Its walking policy is a file inside a wasm app.
VibePlay
Game handheld
Anbernic RG 34XXSP. Every game is a full-screen wasm app, from a signed market or from the handheld next to you.
06 · Build for QingOS
Write an app
in an afternoon.
Rust, compiled to wasm. One manifest. Declare your actions and their risk; the system does the screen, the voice and the asking.
Open the docsNot open source.
Worth seeing run.
We build QingOS with hardware partners. If you make devices where a person and an agent work together, let’s talk.