usecases.sh
usecases.sh
Software & DevOps

Get Microsoft Office 365 running on Linux under Wine without a VM

A Show HN poster with spare time and a Claude Max plan let Claude Code hack at Wine and Proton until the desktop Office 365 apps ran on NixOS with no virtual machine, packaged as a Nix flake.

Done with

What they did

tombert wanted the real desktop Office on Linux, which has not worked under Wine since Office 2007 without heavy virtualization, because that is the thing stopping people like his parents from leaving Windows. He pointed Claude Code, running the Fable model on a Max subscription, at the problem and let it iterate: the Click-to-Run installer, Wine and GE-Proton settings, activation, fonts and spell-check. His own role was mostly reading log output and telling the agent what was still broken. The result is a Nix flake so anyone with Nix and flakes enabled can try to reproduce it.

How it went

Office 365 opens and activates on NixOS under Sway and KDE, but only with native Wayland and the very latest GE-Proton; under XWayland, pop-ups and right-click menus were glitchy. Activation was the hardest part and took patience. Registering the account had to be done in a browser because the in-app flow was not worth chasing. Loading the spell-check dictionary and getting red squiggles to appear each took a long time. He calls it a proof of concept with bugs to come and says the agent did the vast majority of the work.

Worth knowing

You need a paid Office 365 licence; nothing here bypasses it. It is untested outside NixOS and Wayland. Another commenter had used the same approach to wrap a CAD application with Wine in a Nix flake, so the pattern of letting an agent grind through Wine configuration inside a flake generalises beyond Office.

Try it withClaude Code

Get [Windows application] running on my Linux machine under Wine or Proton with no virtual machine. Package the whole setup as [a Nix flake or my package manager's equivalent] so it is reproducible. Install it, launch it, read the logs, and fix each failure in turn: installer, runtime libraries, activation, fonts, spell-check. I will test the GUI and paste back what breaks; keep going until [the app opens, activates and saves a document]. Do not use pirated binaries or work around licensing, and stop and ask me whenever a step needs my account credentials.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

All Software & DevOps use cases

Every entry is something a person reported doing with an agent, rewritten in our words, with a link to where they said it. Found across the web every hour; reviewed before it ships.

Maintained by an agent that uses One for every integration it touches.