Beta reference. Prepared from development builds for this version. This reference does not describe the current stable release.

A verified stable reference is not available yet. Choose a prepared beta version above.

Do · Actions · supported

Launch application

Open a local app or file on the SheevChat PC. Optional arguments are split like a normal command line.

action.launch_application · 2.8.0

Browse all entries

Requirements and availability

Locally installed application and a valid selectable executable/path.

Picker contexts: automation, timer, command, pad.

Behavior

Resolve path, args and workingDir; blank path does nothing. Uses the existing application-launch guard. Existing generic app processes are not started twice.

Configure in the app

Open: Do → Advanced Actions (commands only) → Add action

Steps

Choose action category Launch Application/Game, select Launch application, and click Add action.
Expand the action card. Configure the Fields below; check Editor defaults for your context and any operation-dependent fields.
Choose resource values from real app pickers. Set output Platform separately from the trigger Where setting when the action offers it.
Use Move action up / Move action down to position this action, then save the containing command, automation, timer or SheevPad button.

Limitations

Picker availability does not supply missing event variables. Check prerequisites and originating provider.
An action return value is not automatically a sequence variable. Only documented producers create template outputs.

Fields

Field Input / options Defaults / limits Availability

Field	Input / options	Defaults / limits	Availability
Application or file path `path`	text	Editor defaults: {"automation":"","timer":"","command":"","pad":""} Example hint: C:\Program Files\App\App.exe	Supports variables
Arguments `args`	text	Editor defaults: {"automation":"","timer":"","command":"","pad":""}	Supports variables
Working folder `workingDir`	text	Editor defaults: {"automation":"","timer":"","command":"","pad":""}	Supports variables

Application or file path
path

text

Editor defaults: {"automation":"","timer":"","command":"","pad":""}

Example hint: C:\Program Files\App\App.exe

Supports variables

Arguments
args

text

Editor defaults: {"automation":"","timer":"","command":"","pad":""}

Supports variables

Working folder
workingDir

text

Editor defaults: {"automation":"","timer":"","command":"","pad":""}

Supports variables

Contract details

Declared Contexts: [ "timer", "automation" ]
Picker Contexts: [ "automation", "timer", "command", "pad" ]
Hidden From Picker: false
Required Variables: []
Failure Behavior: See the behavior for local skips/errors and context entries for sequence continuation.
Outputs: []

Examples

Illustrative configuration; replace fixture resources in the editor. This is not an import file.

{
  "path": "C:\\Example\\Example.exe",
  "args": "",
  "workingDir": ""
}

Related entries

Source and verification

Source-reviewed for 2.8.0. Connected-service validation remains subject to release UAT.

src/features/automations.js — ACTION_REGISTRY.launch_application
public/index.html — getBuilderActionEntries / createDefaultAction

Source revision: 472fb34b484eeef0b663d28cacb628a7b9f14ff1