--- name: "fluxbox-remote" section: "1" platform: "linux" package: "fluxbox" version: "1.3.7+221+g36f99b92-1" release: "Arch Linux 2026-11-01" platforms: ["linux"] url: "https://new.carta.tech/fluxbox-remote" --- # fluxbox-remote(1) command line access to key commands for fluxbox(1) ## NAME fluxbox-remote - command line access to key commands for [fluxbox(1)](/fluxbox/1.md) ## SYNOPSIS **fluxbox-remote** *command* ## DESCRIPTION *[fluxbox-remote(1)](/fluxbox-remote/1.md)* is designed to allow scripts to execute most key commands from *[fluxbox(1)](/fluxbox/1.md)*. *[fluxbox-remote(1)](/fluxbox-remote/1.md)* will only work with *[fluxbox(1)](/fluxbox/1.md)*: its communications with *[fluxbox(1)](/fluxbox/1.md)* are not standardized in any way. It is recommended that a standards-based tool such as *[wmctrl(1)](/wmctrl/1.md)* be used whenever possible, in order for scripts to work with other window managers. ## CAVEATS *[fluxbox-remote(1)](/fluxbox-remote/1.md)* uses the X11 protocol to communicate with *[fluxbox(1)](/fluxbox/1.md)*. Therefore, it is possible for any user with access to the *[X(7)](/X/7.md)* server to use *[fluxbox-remote(1)](/fluxbox-remote/1.md)*. For this reason, several key commands have been disabled. Users should be aware of the security implications when enabling *[fluxbox-remote(1)](/fluxbox-remote/1.md)*, especially when using a forwarded *[X(7)](/X/7.md)* connection. ## RESOURCES session.screen0.allowRemoteActions: \ This resource in ~/.fluxbox/init must be set to ‘true’ in order for *[fluxbox-remote(1)](/fluxbox-remote/1.md)* to function. Please read the **CAVEATS** first. ## ENVIRONMENT In order to communicate with *[fluxbox(1)](/fluxbox/1.md)*, the DISPLAY environment variable must be set properly. Usually, the value should be ‘:0.0’. ## AUTHORS This man page written by Mark Tiefenbruck \ ## SEE ALSO [fluxbox(1)](/fluxbox/1.md) [fluxbox-keys(5)](/fluxbox-keys/5.md) [wmctrl(1)](/wmctrl/1.md) ## AUTHOR **Mark Tiefenbruck** \ Author.