Skip to main content
Long story short, they are URLs that are invokable as “shell commands” in Windows. As long as LIV is installed, and has been run once on a system, these commands will work when called from anywhere. Some commands will automatically start LIV, and boot LIV Capture. Some commands won’t do anything if LIV is not already running and active. You can call them manually, using the Windows “Run” prompt (Win+R). You may also create shortcuts to these commands using Windows Explorer: New -> Shortcut, then enter your command. You can then create a hotkey for that shortcut by modifying its properties. Behind the scenes, LIV registers itself as a URI Scheme handler for the liv-app “protocol”. When Windows is asked to execute a URI as a shell command, it will look for a registered handler, and then start that program. When LIV is already running, a second instance of LIV is loaded - it then sends the command to the first instance of LIV before closing itself. Naturally, this process takes some time. We don’t recommend using this interface for high-frequency control of LIV. 
AutoHotkey Example
Run liv.app://...

using System.Diagnostics;

// ...

Process.Start("liv.app://...");

Runtime.getRuntime().exec("liv.app://...");

os.execute('liv.app://...')

const spawn = require('child_process').spawn;
spawn("liv.app://...");