Skip to main content

Desktop app and troubleshooting

The packaged Qontent Tube desktop application combines the local API and web workspace in one executable. It binds to a private loopback address and opens the authenticated workspace in your default browser. It does not require a separately installed Bun or Node.js runtime.

The private release currently provides a Windows x64 executable and a Linux x64 executable. macOS and ARM builds are not included. Review the requirements before you buy before purchasing.

First launch and voice configuration​

On first launch, Qontent Tube asks for a personal voice-generation credential. You may skip setup and continue authoring, but live generation remains unavailable until a credential is configured.

  • Windows protects a saved local credential for the current user with DPAPI.
  • Linux stores it in an owner-only settings directory and requires a 0600 secret file.
  • An operator-supplied managed credential takes precedence and cannot be replaced from the workspace.

The secret is never returned to the browser. Delete or replace a locally managed credential from Rosters & presets without restarting the application.

Starting and stopping​

Launching Qontent Tube again reuses the authenticated running instance. Choose Rosters & presets → Quit Qontent Tube for an explicit graceful shutdown.

The app also shuts down after 30 minutes with no live browser tab and no protected generation or audio-streaming work. Closing one tab does not interrupt active work.

Browser did not open​

Start the application with --no-open and open the one-time URL printed by the launcher. The short-lived bootstrap URL becomes a private browser session and cannot be reused after consumption.

Linux says the file is not executable​

Mark the downloaded Linux file as executable, then run it:

chmod +x qontent-tube-*-linux-x64
./qontent-tube-*-linux-x64

Generation is unavailable​

Open Rosters & presets and check the voice-generation status. Authoring and playback of existing clips still work without a configured credential. Generation errors are intentionally sanitized and never include secret or provider model details.

External changes are not visible​

Confirm that the file is a regular top-level .md file in the selected project's folder, then use the compact Refresh action. See Work with files and storage for the complete discovery rules.

A capture scene won't render​

Open Storyboard → Validate & render and fix the errors it lists. Errors have no override, so a missing file or unfinished privacy review must be resolved. To check from a terminal, see the capture commands.

Your data after an upgrade or uninstall​

Release upgrades and uninstall intentionally preserve .qontent-tube and any separately configured content directory. Back up that directory using your normal file backup workflow.