---
title: "How do I let Fluxer read my keyboard directly on Linux?"
description: "Join the input group and turn on \\\"Use direct input device access\\\" to get push-to-talk and system-wide keybinds that other apps can still use, in the Fluxer desktop app on Linux."
url: "https://fluxer.com/help/linux-direct-input"
language: "en"
last_updated: "2026-11-16"
category: "Features and apps"
---

> Index of Fluxer's official pages for AI agents: https://fluxer.com/llms.txt
> Index of this topic: https://fluxer.com/help/category/features/llms.txt
> Links to Fluxer pages go to their Markdown versions when they have one. For other Fluxer help, policy or blog links, remove any #section part and add .md to the end.

# How do I let Fluxer read my keyboard directly on Linux?

Join the input group and turn on \"Use direct input device access\" to get push-to-talk and system-wide keybinds that other apps can still use, in the Fluxer desktop app on Linux.

On Linux, the Fluxer desktop app can read your keyboard and mouse directly for push-to-talk and other [system-wide keybinds](https://fluxer.com/help/keybinds.md). It only offers this once you've given your Linux account permission to read input devices, and you turn it on with the "Use direct input device access" switch under "System-wide keybinds" in "Keybinds".

## How do I turn on direct input device access?

On most Linux distributions, you get the permission by joining the `input` group. Run this command in a terminal and type your password when it asks for it.

```sh
sudo usermod -aG input $USER
```

Then sign out and back in and open Fluxer. Go to "Keybinds" under "App settings" in "User settings" and turn on "Use direct input device access" under "System-wide keybinds". The switch stays hidden until your account can read a keyboard.

## What changes when I turn it on?

Your desktop no longer handles Fluxer's system-wide keybinds, so your keys keep working in all your other apps too. A push-to-talk key such as C still types the letter C everywhere else, and you can also bind push-to-talk to a side button on your mouse.

It also works on Wayland desktops that don't offer system-wide keybinds, where Fluxer's keybinds otherwise only work while Fluxer is focused. On X11, Fluxer already listens for system-wide keybinds without this permission, and other apps still get your keys.

Push-to-talk then only uses the key you set in Fluxer's "Voice & video" settings. If you haven't set one there, your microphone uses voice activity instead.

## Why isn't this on by default?

Reading input devices directly lets an app see every key you press, which is how a keylogger works. Most Linux distributions keep keyboards locked away from the apps you run for that reason, and we'd rather you give Fluxer that access on purpose.

Older versions of the desktop app showed a banner that asked for your password and set this up for you, which felt sketchy to many people. The desktop app now never asks for admin rights, and the setting stays off until you join the `input` group yourself.

## Does it work with the Flatpak?

Yes. The [Flatpak](https://fluxer.com/help/install-fluxer-with-flatpak.md) can already see your input devices, so joining the `input` group on your computer is the only step, just like with the other packages.

## How do I join the input group on Fedora Silverblue or NixOS?

On Fedora Silverblue, Kinoite and other Fedora Atomic desktops, `usermod` can't find the `input` group. Copy it from `/usr/lib/group` to `/etc/group` first.

```sh
grep -E '^input:' /usr/lib/group | sudo tee -a /etc/group
sudo usermod -aG input $USER
```

On NixOS, add `"input"` to `extraGroups` for your user in your NixOS configuration and rebuild. On any distribution, sign out and back in afterward.

## Why doesn't the switch show up?

Run `groups` in a new terminal. If `input` isn't in the list, your login session still has your old groups. Some desktops keep parts of your session running after you sign out, so restart your computer and run `groups` again to check that `input` is there.

If `input` is in the list, quit Fluxer from its tray icon and open it again, because Fluxer checks for the permission when it starts. The switch is also hidden in safe mode and when you start Fluxer with an option that sets the input mode, such as `--fluxer-input-hook`.

## How do I turn it off again?

Turn off "Use direct input device access" to go back to your desktop's keybinds. To take the permission away from your account too, run this command and sign out and back in.

```sh
sudo gpasswd -d $USER input
```

If an older version of the desktop app set this up for you, it may also have added the file `/etc/udev/rules.d/70-fluxer-input.rules`. Fluxer leaves it alone, so delete it with `sudo rm` and restart your computer to take that access away too.

## Is direct input device access safe?

Fluxer opens your input devices read-only, never takes a key away from other apps and only reads them while your login session is the active one. It only uses the keybinds you set in Fluxer, and it doesn't save any other key or send it off your device.

The `input` group lets every program you run on your computer read your keyboard, not only Fluxer, so only join it if you're comfortable with that. You can check how Fluxer handles input devices yourself in the [desktop app's source code on GitHub](https://github.com/fluxerapp/fluxer/tree/main/fluxer_desktop/native/linux-evdev).

---

Canonical page: https://fluxer.com/help/linux-direct-input

Last updated on November 16, 2026
