CaptureGem Data Locations and Automation Options
The normal CaptureGem workflow uses the desktop app and Monitor tab. The desktop executable does not provide customer flags such as --headless or --export-metadata. On Linux x86_64, the bundled recorderd binary can also run without the desktop. Follow the official standalone Linux guide for the required matching binaries, service setup, and API instructions. Its HTTP and proxy ports have no authentication and must be blocked from untrusted networks.
Find the active data directory
An explicit CAPTUREGEM_DATA_DIR environment override selects a separate data profile. Without one, a new macOS profile uses ~/Library/Application Support/capturegem, a new Windows profile uses %LOCALAPPDATA%\capturegem, and Linux uses ~/CaptureGem_Data. Existing macOS and Windows installs can use older locations. When both old and new folders have settings, the desktop may select the newer one while the recorder daemon still uses a legacy folder containing config.json. Check both folders and logs before moving files; an explicit override aligns both processes.
Automate around finished files
For personal backup or post-processing, use a separate tool on finished, verified recordings. Keep the original and any temporary or retained source files until playback and backup checks pass. Do not run scripts against an active recording folder or assume CaptureGem has an on_stop hook.
See file locations, archiving finished recordings, and desktop and standalone Linux options.
Loading comments...