RESENTMENT OS is an AI operating system built on its own kernel. Agents hold leases, not permissions, and every one expires. The whole system is one hash. Any model provider works with your key, or a model runs on your own GPU inside the browser, and nothing leaves your machine.
Runs here, in the page. Add a key in its Settings, or pick a model that runs on your GPU. Everything it stores stays in this browser.
Most "AI operating systems" are a chat window with file access. This one is built on a kernel whose ideas the desktop repeats at its own level, so the same rules hold in the boot sector and in the conversation.
In the kernel, every capability carries a Kaalka seal with a time window. On the desktop, every permission an agent holds is a lease with a deadline. There is no "allow forever" button, so a forgotten grant stops working by itself.
How leases work →7d4a1f0e83c25b9a6f1e0d4c8b3a7e2f
Every kernel object is a node in a Merkle DAG and the machine has one root. Every file and setting on the desktop is a node too, and the OS has one root you can snapshot, diff and attest. Timestamps are out, so two machines with the same content agree. Keys are never in it.
What is hashed, and what is not →| id | state | tokens | |
|---|---|---|---|
| 1 | running | 41 208 | kill |
| 2 | waiting | 3 114 | kill |
| 3 | idle | 128 990 | kill |
Inference in the kernel is a scheduling class with admission control and a budget. An agent on the desktop has a state, a token budget, a row in the process table, and a kill button. Killing it revokes its leases.
The agent loop →tool fs_write /home/documents/plan.mdfs.write /home/documents/plan.md cause #41undo to #40 reversed 2The kernel records events in causal order for deterministic replay. The desktop writes every tool call to a ledger, and every file change names the call that caused it. Undo restores the files and is itself an entry. History is never deleted.
The ledger →The desktop speaks three wire formats, which is every model API anyone sells, and it can run a model on your own GPU inside the tab with no server and no key. Paste a key or pick a local model, done. A key is stored in your browser, optionally sealed under a passphrase, and sent to exactly one place: the provider's own endpoint.
[ 0.021841] kaalka temporal keying active, epoch 29798350 [ 0.028901] cap capability system ready: 24 types, sealed [ 0.082106] smp 4 of 4 processors started [ 0.118176] selftest all 7 self-tests passed [ 0.119217] boot boot complete in 119 ms, 505.4 MiB free RESENTMENT 2.0.0 (kaalachakra) x86_64 4 cpu resentment> .run /boot/bin/facts.she not allowed to system. This script was not granted permission to read the runtime graph. resentment> .allow all granted every permission resentment> .run /boot/bin/facts.she arch=x86_64 cpus=4 digest=7d4a1f0e83c25b9a6f1e0d4c8b3a7e2f5d9c1b8a4e7f0c3d6a9b2e5f8c1d4a7b angles=142.5,87.0,55.5
The RESENTMENT kernel is a from-scratch, capability-secure, AI-native kernel for x86_64, ARM64 and RISC-V: a transformer forward pass on its own operators, a SHE shell where programs start with no permissions, and a Merkle root for the whole machine. 1440 host assertions, six QEMU targets, seven self-tests on every boot.
It has a serial console and no network stack yet, so the desktop reaches it through a small bridge that relays the serial line over a WebSocket. Attach, and the Kernel window is a live console into ring 0, the Digest window shows the machine's root beside the desktop's, and the agent gets a kernel_eval tool gated by the kernel's own grants.
A status table that overstates is worse than none.
| Part | State |
|---|---|
| Desktop: windows, dock, intent bar, ten apps, offline | working, deployed on this page |
| Providers: Anthropic, OpenAI-compatible, Gemini; streaming and tool calls | working, tested against recorded streams |
| Local models: inside the browser on WebGPU, or through Ollama, LM Studio and any local server | working; in-browser needs a WebGPU browser and one download per model |
| Leases, ledger with undo, digest with snapshot, diff and attest | working, tested |
| Vault: plain, or AES-GCM under a passphrase | working, tested |
| Bridge: QEMU's serial line over a WebSocket | working, tested against a fake kernel and against QEMU in CI |
| The kernel boots with the OS ramdisk and answers the desktop | working on x86_64 in CI; aarch64 and riscv64 build and attach the same way |
| The desktop running inside the kernel | not yet — the kernel needs a network stack and a compositor first; both are on its roadmap |
Today the desktop runs in a browser on a host and drives the kernel. The direction is for the desktop to run on the kernel, and every choice here — no server, no build step, no ambient authority, one hash — is made so that move is a port and not a rewrite. The roadmap says what comes next and what will not.
Right here, right now. Add a key in Settings. Nothing to install and nothing leaves your browser.
Open the OS →It is an installable app: open it, then use your browser's "install" or "add to home screen". It works offline, except for the model.
From inside the OSgit clone --recursive -b v2.0.0 https://github.com/ni-sh-a-char/RESENTMENT.git
cd RESENTMENT
make toolchain
make run