Show HN: Aurion OS, A 1.8MB OS with a browser, try it live (C/x86 ASM)
Show HN (score: 5)Description
Since then, the OS has gone from Beta to v1.0 Release with a lot of improvements:
Blaze Browser: HTML/CSS/JS rendering with tabs and a developer console (local only, no full http/https support for now) Installer with user account setup and app selection Multi-resolution support (800x600 to 2560x1440, I plan to add 4096x2160 pixels in next versions) Unix-style luka@aurion prompt Serbian keyboard layout Python interpreter and Make build system 50+ terminal commands Window manager improvements and bug fixes
1.8MB ISO (entire OS including the browser and GUI) Supports QEMU, VirtualBox, VMware, and v86
You can try it live in the link above, or grab the ISO from GitHub: https://github.com/Luka12-dev/AurionOS
Built solo as a hobby/learning project. I'm 13. I'd love any feedback, suggestions!
More from Show
Show HN: Ccgs – Collaborative Claude Code sessions, stored in Git branches
Show HN: Ccgs – Collaborative Claude Code sessions, stored in Git branches My team uses Claude Code daily, and the sessions have become some of the most useful artifacts we produce. But they're trapped in ~/.claude/projects/ on whichever laptop they happened on. There's no good way to hand a colleague "the session where I untangled the migration" so they can claude --resume it and keep going from where I left off. Enter ccgs: Share Claude Code sessions through an orphan branch (@ccgs/<name>) in your existing repo's remote<p>- Session files carry the author's absolute paths. On pull, ccgs rewrites the working dir back to your path so resume actually works — surgically editing only the structural cwd field, not a blind find-and-replace that would happily corrupt the transcript.<p>- Everything goes through git plumbing (hash-object/commit-tree/update-ref) against a throwaway index. It never touches your working tree, index, or current branch, and it's fine with a dirty tree. It will not git checkout something behind your back.<p>To try it without installing: `npx claude-git-sessions`. This also incidentally allows you to move a directory and carry the claude code transcripts with it (just push first, then move the directory, then pull)<p>IMPORTANT CAVEAT: Unless you have a very good security hygiene, your Claude Code sessions are likely full of sensitive information such as environment secrets. Use with caution and avoid using on public repositories. Branches used by ccgs are prefixed by `@ccgs/` so you can easily filter them out.<p><i>This project was written by and with Claude Code. This Show HN was not.</i><p>(Reposted with URL fixed)
No other tools from this source yet.