InterGenOS
A Linux distribution built entirely from source with a custom package manager, a tiered local AI assistant, and integrated AI-driven security auditing.
Website · Updates · Documentation · InterGen Studios
x86_64 UEFI live ISO · 9.8 GiB · sha256 4608b40b9d8854a36489a435776e9bb08e20c7dd03cadf02929632b2cfe5b7d0 — checksum file and the signature over it
Verify before you write it: check the signature on the checksum file, then check the image against the checksum — the steps are here.
Signed on-hardware with the release key, fingerprint 5597 A3E0 587B 2530 06D0 DD7B 8C50 8261 8208 3050 — the same key signs the image checksum, the release tag and the package mirror index.
InterGenOS puts the user in control of their own machine. Every package is compiled from source with deliberate choices. Every design decision serves one purpose: giving people a system they understand, can modify, and can trust.
InterGen, the local AI assistant, doesn't just help you use your system — it helps you understand and secure it. It runs on everything from a laptop with no discrete graphics to a GPU workstation, fully offline, choosing its model tier from the graphics hardware it finds. Every tier is multimodal. InterGen Sentinel — its security-scanner layer — checks every MCP tool call before it reaches a tool: a deterministic rules scanner that is always on, and a local model-backed classifier (Local-Qwen, your local Qwen model) that attaches when its configured model is present and verified.
"Fully offline" means the local model: web searches and page retrieval you request, and Phone-A-Friend requests you approve, are the only paths that touch the network, and each is your choice.
Screenshots
GNOME 49.4 on Wayland with the InterGenOS shell theme.
Desktop ships with the first-party InterGenOS icon theme as default (promoted at 1.4; it inherits Adwaita and hicolor for full application coverage). Papirus-Dark and the Cybernetic Blue icon theme by SethStormR ship as featured alternates, switchable in the first-boot Welcomer or later with GNOME Tweaks. Typography is Inter for the interface — shipped as the variable family Inter Variable, which is the family name the desktop defaults request — paired with JetBrains Mono on terminal and code surfaces, over a system-wide prefer-dark colour scheme.
Security-Only Alignment
InterGenOS is built for a world where AI-assisted vulnerability discovery is a foregone conclusion, not a theoretical threat. Recent frontier-AI evaluations have demonstrated working-exploit yields two orders of magnitude above the previous generation, with broad benchmark coverage across major operating systems and browsers — and that capability will proliferate. We build this distribution assuming adversaries have superhuman vulnerability discovery and make every design decision with that in mind. Secure Boot is available and strongly advised: every image ships a fully signed boot chain, and enabling Secure Boot with your machine's enrolled key makes the firmware enforce it. Every package choice is a security choice. Nothing that hides how the system works gets shipped.
Security is not first. It is only.
The Forge Secure Boot chain — each link verifies the next, anchored to a Machine Owner Key the installer generates per machine:
flowchart TD
FW["UEFI firmware<br/>(Secure Boot on)"] --> E1[" trusts MS UEFI CA "] --> SHIM["shim<br/>Microsoft-signed"]
SHIM --> E2[" verifies SBAT + signature "] --> GRUB["GRUB<br/>MOK-signed"]
GRUB --> E3[" verifies "] --> UKI["Unified Kernel Image<br/>MOK-signed"]
UKI --> KRN["kernel<br/>lockdown=integrity<br/>module sig_enforce"]
MOK(["Your Machine Owner Key<br/>enrolled once — the trust anchor"]) -.-> S1[" signs "] -.-> GRUB
MOK -.-> S2[" signs "] -.-> UKI
classDef lab fill:#4b4b4b,color:#ffffff,stroke:none;
class E1,E2,E3,S1,S2 lab;
The Prime Directive
InterGenOS exists to put the user in control of their own machine. Every design decision, every default, every included component must serve this purpose: giving people a system they understand, can modify, and can trust. Any complexity that doesn't serve the user — or that hides how the system works — is not welcome, regardless of how conventional it may be.
The Prime Directive and the security-only alignment above are complementary: a machine the user cannot trust is a machine they do not control.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
