Install on Linux
Linux is in release testing. Here is how install works the day it ships: AppImage or .deb, plus an unlocked desktop keyring.
Mac and Windows today. Linux is in release testing, and its download appears on the download page the day it ships. When it does, your whole team runs on Linux: the org chart, chats, memory, routines, every model.
Pick a package
Fluf for Linux will ship as an AppImage and a .deb package. Until the Linux row on the download page shows Download for Linux, there is nothing to download. Once it does, pick the file that matches your CPU architecture.
- AppImage: mark the file as executable in your file manager (or
chmod +x), then launch it. Some distributions need an AppImage support package first. - .deb: open it in your package installer, install, and launch Fluf from the app menu.
Unlock your keyring
Fluf keeps keys in your desktop's Secret Service keyring. Sign in to a graphical desktop session and unlock the keyring before adding a key. If Fluf says the credential store is unavailable, fix the keyring; never put a key in a chat or a config file instead.
Connect a model
Meet Pom, then add an API key in Settings › AI connections, or let Fluf run your installed Claude Code or Codex, signed in with your own login. Your bots work while the computer is on and awake, with Fluf running.
Computer use on Linux
Computer use needs a desktop session: X11, or Wayland after you approve your system's screen-sharing prompt. Fluf checks this for you. With no desktop session, bots can't control apps, but they still browse, write, research and run routines.
Updates and removal
Update through the path that matches your package: your package manager for .deb, the in-app update for an AppImage kept somewhere you can write to. Back up work before removing local data. Removing the app doesn't cancel a paid plan.
Next: Hire your team · Connect your AI · Troubleshooting