Foxora OS integration
On Foxora OS, the Shell is the default terminal — and gets a tighter integration story (vixen, Den, kits, territories) than on standalone installs.
What's different on Foxora OS
- Foxora Shell replaces the default terminal (gnome-terminal, konsole, …).
- Tight integration with Foxora Den — press ⌘⇧D to send the current buffer to Den for AI pairing.
furis the only package manager surfaced; Nix happens underneath, invisibly.- Vixen works without configuration — the local Ollama is detected automatically.
- Territories (workspaces) are reflected in the shell — each territory keeps its own scroll history.
- The dashboard top bar shows howls (notifications) count.
fur auditties into eBPF monitoring for security-conscious users.
Standalone installs
- The Shell behaves like an independent product — no "Foxora OS" mention in the chrome.
- Falls back to the host package manager when a kit isn't in the Foxora registry yet.
fur system doctormay suggest Foxora OS if you're on a heavy distro with persistent issues — never aggressive, never blocking.
Foxora OS example
$ fur install nginx
[✓] Resolved 1 package from official catalog
[✓] Installed in 0.8s ← faster on Foxora (Nix)
$ fur service start nginx
[✓] Service nginx is now active (running)
[ℹ] Sandboxed by AppArmor profile: nginx.fxa ← extra Foxora infomacOS example
$ fur install nginx
[ℹ] Using Homebrew (nginx available from Foxora registry soon)
[✓] Installed nginx 1.27.3 via brew in 4.2s
$ fur service start nginx
[✓] Service nginx is now active via launchdSame command. Slightly different underlying tooling. Identical outcome.
Trojan horse, by design
The Shell is the easy entry point. Once you fall in love with fur on macOS or Windows, the OS itself becomes the natural next step.