Boot into your workflow, not your setup weekend.
Every laptop you own has one weekend of setup blocking it from being a working agentic dev machine. vinOS ships that weekend already done — Hyprland, Ollama, Claude Code, sensible defaults, and 88 helper commands, all wired on first boot. You write code. It handles the rest.
The three things you're paying for right now.
The setup weekend.
A functional Wayland desktop is a shopping list: compositor, bar, launcher, terminal, lock screen, notification daemon, clipboard, screenshot pipeline. Then themes. Then keybindings. Then font hinting.
The API bill.
You're routing every prompt to a frontier model — including the summarize / refactor / extract grunt work a local 7B can handle for free. Your monthly Claude bill is quietly subsidizing tasks that don't need it.
The data leaving your machine.
Every unfamiliar prompt, every codebase excerpt, every internal doc — sent to someone else's servers. Fine for public work. Suddenly not fine when a client hands you a repo.
What vinOS does instead.
Zero-config, first boot.
Hyprland + waybar + walker + foot + hyprlock, tokyo-night themed. Every driver detected, every service tuned. No dotfile chase. No community wiki.
vinos-doctorprints green.Local for the 80%.
Super+A opens Ollama chat with the model you pick. Grunt work — summarize, refactor, extract, draft, test — runs on your GPU for free. Zero API tokens burned.
Frontier for the 20%.
Super+Shift+A opens Claude Code in your project. Deep reasoning, big context, final polish — over the API, only when it matters. Your bill covers judgment, not busywork.
Every helper is a shell script.
88
vinos-*commands, each under 80 lines, every oneshellcheck-clean. Read them, fork them, replace them. Nothing hidden.
vinos-doctor → PASS = 26 · FAIL = 0 · SKIP = 3. Real output from a fresh boot.Ship faster. Local first.
Flash a USB. Boot. In fifteen minutes, your daily driver runs local LLMs and Claude Code. Every subsequent boot: five seconds to a working workspace.