Vizsla OS was built in a matter of weeks by one man in Florida and an AI he directs — talking, deciding, and arguing in plain language, often sixteen hours a day. It takes the best of computing from the 1970s through today — old favorites, kept — and adds things none of them have ever had. It is deliberately different in the ways that matter: not just private, but kind. It is a labor of love, and it is not finished listening.
How you’ll notice it
- Nothing in Vizsla requires an account. Apps may offer one; the system never demands one.
- Updates never lock you out of your own machine in the middle of your work. They wait until you’re away, the machine is plugged in, and the network is unmetered — and if you say “not yet,” they say “fair enough” and tell you what they’re waiting for, in plain words.
- If an app disappears and the system doesn’t know why, it asks — once, gently: “hi it’s me. Sorry to bother but I’m not sure if you want to uninstall this. Please let me know if you want it reinstalled or not. No worries either way.” If you removed it on purpose, it never asks at all.
- The machine manages itself across the whole house. Software is built once and lands, verified, on every computer that can run it. Decisions that need a human collect in one calm inbox instead of ambushing you app by app.
- It is one system in every shape — desktop, tablet, TV, console, phone, dash — the same apps and files, rearranged, never reduced.
How it was made
Vizsla was not written by a company, a team, or a foundation. It was built in weeks — the record runs from late September to late October 2026 — by one person and an AI, working together in long daily sessions that often ran sixteen hours or more, including middle-of-the-night emergency reboots across the three computers that now run it. That is the honest version, and it doesn’t need inflating: in that span the work produced a working system of dozens of apps, a design language, an installer, and a fleet of three machines that keep themselves in sync — work that used to be measured in team-years.
The weeks are only the visible part. The ideas were written down long before anyone built them: a Linux wishlist he started in 2019 and kept updating for five years, a 2021 sheet that already names a “washing machine” app for stripping metadata from files and sketches the system profiler and the film renamer almost as shipped, and — in June and July of 2026 — a complete written blueprint for a self-hosted system of his own whose maintenance checklist became this system’s own job description. Vizsla was built in a matter of weeks in the fall of 2026. It had been planned, on paper, for years.
The method matters more than the hours. One human supplies the vision, the judgment, the taste, and the final word. The AI supplies velocity: drafting, building, testing, and checking at a speed no single pair of hands has. Neither half works alone. Software this considered doesn’t come from a person typing for a decade, and it doesn’t come from a machine left unsupervised either. It comes from the conversation — thousands of decisions, made out loud, on the record, one at a time.
The man behind it
Richard Garrison lives in Leesburg, Florida. He was raised in Columbus Junction, Iowa, reads fast, and writes short. He holds a BA in English and Anthropology from the University of Iowa, and he spent his career in human resources and healthcare operations — most recently as a Senior HR Coordinator in Dade City, Florida — which is to say he spent years watching ordinary people fight ordinary software, and learning exactly where it hurts them.
He has ADHD, and he will tell you himself what that means here: every project arrives in his head as a whole little world, already finished, and building is the act of dragging one world at a time into reality before the next one crowds in. Vizsla is shaped by that mind on purpose. It ranks what needs you by stakes, not by noise. It never demands, nags, or pulses for attention. It keeps ten thousand ideas from getting lost by writing them down and building them in the open. The system a scattered, relentless person needed turned out to be the system that is calm for everybody.
He shares the house — and the testing — with a Rat Terrier named Mandy, who has strong opinions about none of this and supervises anyway.
Vibe coding, honestly
What built Vizsla has a name, and the name currently has a bad reputation: vibe coding. It means directing AI systems in natural language — describing what you want, judging what comes back, steering — instead of writing every line by hand. Let’s be fair to the reputation first. The practice is in its infancy. Used carelessly, it produces slop: code nobody understands, features that demo well and die in production, and real security holes left by people who never looked. The slur exists for a reason, and anyone who tells you otherwise is selling something.
Now the other half, which this project exists to prove. Vibe coding puts development speed on a curve software has never had — not a little faster, a different kind of fast — because the bottleneck moves from typing to thinking. And here is the part the critics miss: security and quality assurance get better, not worse, when the speed is spent on them. The hours a solo developer never had for a second review pass, a test suite, a security audit, an install verified hash-by-hash on every machine — the speed makes those affordable. Vizsla’s whole working method is the exhibit: every app specified before it is built, every claim checked against the machine, every install proven, every failure written down and turned into a rule so it happens once. A lone careful human used to have to choose between shipping and checking. That choice is what is actually ending.
The honest summary: the infancy is real, the slop is real, and the future is still this. Judgment was always the scarce ingredient in software. Now it’s the only one you have to bring.
Not a derivative
Vizsla stands on good ideas and says so — it takes the best from fifty years of computing, the 1970s pioneers through today’s systems: calm notification manners, a search that runs on your own machine, old favorites kept alive on purpose. But several things in it have not appeared in any other operating system:
- A fleet that installs itself. One catalog is the truth; every machine in the house is kept to it automatically, each install verified, each drift noticed.
- Pass or Paws. Every decision the system needs from its human — every one — collects in a single decision inbox, to be answered in one sitting, in plain words. No other system asks its owner this politely, or this rarely.
- A color law you can measure. Every app’s color holds a recorded seat in one family registry, kept a measurable distance from every other seat — no clashes, ever, enforced by the build itself.
- The Baking Hour. A new Vizsla machine sits and gestates for at least an hour after install — indexing, warming, pre-fetching — so it is fabulous the first time you touch it, not the fiftieth.
- Triage by stakes. Your day surface ranks what needs you by what it costs you, with the remedy attached — not by which app shouted loudest.
- One system, every shape — the same system and apps across desktop, tablet, TV, console, phone, and dash, ready before the hardware is.
And underneath the features, the deliberate difference: kindness as a design property. Not just privacy — though your files live on your machines, no account is required, and a “no” from you is recorded and never re-asked. Kindness in the small mechanics: an update that won’t hijack your evening, an alert that apologizes for existing, a button that is calm instead of demanding. Operating systems have competed on power and on polish for forty years. Nobody competed on being kind to the person at the keyboard. That is the whole idea here.
A smidge of history
Every operating system you have ever used was built by hundreds or thousands of people over years, inside companies that could afford both. The personal computer’s founding myth — one person, a garage, a machine built out of love for what computers could be — quietly became impossible as systems grew. Vizsla is a bet that it just became possible again: that the garage is back, it seats one human and one AI, and what comes out of it can stand next to the big systems on the merits — different where it counts, honest about where it borrows, and built by someone who has to live in it every day.
Deeper
If you want the receipts, this manual is full of them: the doctrine topics on this shelf are the rules the system was actually built under — no means no, local first, answers with receipts, buttons are buttons. The story above is the short version of those rules with a face on it.
This is truly a labor of love, built by a man who needed it and an AI that argues with him when he’s wrong. It will get better the way it got built: out loud, on the record, one decision at a time. So — tell us what would make it better. Constructive feedback is not a suggestion box here; it is the development process. If something is clumsy, say so. If something is missing, name it. The next version of this page will be written the same way this one was: by listening, and then building what we heard.