Working name · release candidate in preparation
An operating system that does not start from the typewriter.
Files, windows, menus and the keyboard-and-mouse ritual all descend from the paper office. BritOS is an AI-first Linux for laptops that starts from what you want done. You bring your own AI key, you own the audit log, and your phone approves anything sensitive.
Pre-release. The first test image has not yet been booted on real hardware. Each feature below says whether it is in that image, built but switched off, or still a design.
Ready
The B-O-S mark is also the system’s activity indicator: still when idle, moving only while something is working. Tap it to run one cycle. Illustration, not a screenshot.
This is a free personal-use edition under our own licence (all rights reserved; commercial use needs a separate licence). It is provided as is, without warranty and without liability. It includes several experimental features that may not meet your expectations, and a test build can fail to boot, lose data on a disk you point it at, or behave unexpectedly. Use a spare laptop or a USB stick you can wipe. Terms · Which parts are experimental
Why another distro?
Linux distributions differ in packaging, update policy and defaults. None of them rethinks the interface for an assistant that can act on your behalf.
So we did not write another base. BritOS reuses a proven one: Fedora’s image-based system with stock KDE Plasma, unchanged. Our effort goes into three things that sit on top.
- The interaction layer. You state an intent; the system proposes a plan and shows the cost before it works. Windows and menus are still there when you want them.
- The safety model. Content is data, never instructions. What an assistant may do is enforced below the model, and sensitive actions need your phone.
- Ownership. Your keys stay on your device, the audit log is yours to read and verify, and the model provider is your choice.
No app hunting, no launcher
An operating system built around an assistant should not make you go looking for an app, or imitate an OS that is a glorified app launcher. Say what you want. The system works out how to get it.
Apps, the browser and the Classic desktop mode (plain KDE Plasma) remain available. Nothing is taken away; you are just not required to hunt for them.
Say it and it connects
Built, off in the first imageAsk to connect a service, for example “connect my Zoho apps”. The system looks for the vendor’s official MCP server or API, prefers a consent screen you click through over long-lived keys, and starts read-only. You log in yourself; the assistant never sees your passwords. Tested against fake services only.
Views, not app windows
Built, off in the first imageResults are drawn from a fixed, safe set of components: cards, tables, charts, documents, forms, timelines, text and speech. Never code or HTML supplied by a model or a service. Ask for a different shape and the preference is remembered as a rule you can edit.
Knowledge work done by the system
Built, off in the first imageDocuments, decks, spreadsheets, briefs and research, written as new files with a source for each claim. It never overwrites your originals, and sending anything is a separate step you confirm.
It extends itself, with permission
Built, off, untestedPreferences, skills, views, automations and, last, small generated tools. Each shows what it can touch before you approve it, cannot widen its own permissions, and can be undone. The trusted parts of the system are out of its reach.
Tutorials generated on demand
In the first image: the first-run tourAsk “how do I…” and a walkthrough is generated from what the system actually has, with captions always shown. Only the first-run tour is written by hand. Model-written tours are untested; templates cover the gap.
What it is built to do
The machine is your assistant
In the first image: first-run and chat windowA single place to ask, with the cost shown before work starts. The first image has a chat window and a guided first-run. No real AI provider has yet been exercised by us end to end.
Sovereign, bring your own key
In the first imagePaste a key from almost any supported provider; the system recognises it without sending it to the wrong place. The key is typed on the laptop and held by the credential broker. It is never sent to us, shown again or given to the model.
A local model, if you want one
Built, off in the first imageWhere the machine can run one, an open-weight model on the laptop can handle private work. It is signed, checksummed and downloaded on request. The first image has no release key, so it stays off.
Your phone approves
In the first image: pairingRoot operations, payments, changes to who can approve and erasing the audit log are approved on your enrolled phone and nowhere else. A password, fingerprint, face, spoken yes or click on the laptop never counts. Most of these actions are switched off in the first image.
It never speaks sensitive information
Built; voice is off in the first imageOne guard sits in front of every text-to-speech output and cannot be switched off. Passwords, codes, keys, card numbers and approval text are never spoken; private content is shown on screen instead. Heuristic detection, so it can miss things.
An audit log you own
In the first image, lower-assurance modeModel calls, tool calls, approvals and device use are recorded in a hash-chained log on your machine. You can verify it and ask the assistant about it. It makes tampering visible; it does not make it impossible.
What is real today
Taken from the project’s own release notes. “In the first image” means switched on in the first bootable test image. Nothing has been booted on real hardware yet, so every row is unverified on a real machine.
How to read the chips
- In the first image
- Built, off
- Not shipped
- Unverified
- Testers only
Built means the code and its tests exist. Unverified means it has not run on real hardware, which today is every row.
| Feature | State | Note |
|---|---|---|
| KDE Plasma desktop, Classic mode | In the first image Unverified | Stock Plasma on an image-based Fedora system. Always available. |
| First-run window, connect your AI, assistant chat | In the first image Unverified | Your own key, typed on the laptop. Real provider calls not yet exercised. |
| Phone pairing (Link app or web companion) | In the first image Unverified | The feature most likely to need a fix (firewall, local network). |
| Audit log, credential broker, spending limits | In the first image Unverified | Audit runs in a labelled lower-assurance mode. |
| Voice, camera gestures, local model | Built, off Unverified | Models not downloaded or verified; no microphone or camera pipeline tested. |
| Connectors, knowledge work, extensions, cloud drives | Built, off Unverified | Built against fakes; real vendor flows untested. |
| Payments wallet and browser autofill | Built, off Unverified | Fake provider only. The system never holds money or card numbers; no real payment provider is connected. |
| Root helper and agent worker | Built, off Unverified | Shipped but not enabled; they need setup steps no installer performs yet. |
| Whisper bar, glance edge and other Plasma widgets | Not shipped Unverified | Need a compiled bridge that has not yet been built. The shell is two ordinary windows. |
| Always-on-top approval screen on the laptop | Not built Unverified | Approvals are answered on the phone only. |
What we do not claim
- No testimonials, user numbers or benchmarks. There are no users yet.
- No claim that it boots on your laptop. The image is x86_64 only and untested on real hardware.
- No claim of perfect security. It is built so that a fooled model can do less damage; it has had no outside review yet.
- Secure Boot, TPM sealing, Wi-Fi, sound, camera and battery behaviour are unverified.
Contact
- hello@getbritos.com TODO owner: confirm this mailbox exists (general, privacy and security)
- Registered office
- Montclare, Orpington Bypass, Badgers Mount TN14 7AG
Operated by Polyglyph Analytica Ltd.