Does BetterDisplay need to be running for CLI display commands?

Yes. Commands that change brightness, switch modes or manage virtual screens send requests to the running BetterDisplay app. The command-line companion does not independently replace the app’s display controllers.

Start BetterDisplay first, then check Settings > Application > Integration > Enable CLI access and notification based integration. A request can time out if the app is not running or is not accepting notifications. Calling the executable inside the app bundle with a recognized integration operation also sends a request to the running app. Start BetterDisplay normally before using that method, too.

If you bind commands to keys in another automation app, keep BetterDisplay running for those bindings to work. Its Settings window does not need to stay open. HTTP requests also need the app running. To use them, turn on Enable integrated HTTP server.

See setting up command-line access and CLI examples for setup and syntax. Scripted license management is a separate command-line mode with its own instructions.