terminal-opener

Topics in the source

• Terminal Opener
• Launch a command
• Recover from terminal configuration
• Inspect before launch

Use scripts/open-terminal.js to preserve an executable and every argument as separate process entries. Never interpolate a shell command string. Keep every spawn on shell: false. Default to a non-launching plan. Use --launch only after the user explicitly requests a real window and the argv has been reviewed. The launched process inherits the full environment of the calling process, including secret-bearing variables. The launcher does not filter the environment. Run it from a shell whose environment is safe to expose to the target command. Pass launcher options before --, then pass exactly one executable followed by its argument array: Run normal mode first. Let WezTerm try its mux with a new window, then let the launcher fall back to a detached wezterm start process if the mux is not available. When fallback is used, read muxFailure from JSON output (or the human-readable failure line) to diagnose why the mux path failed. Add --recover or --standalone when user configuration or mux state may interfere with the requested command. Start a detached WezTerm process with: Expect recovery mode to skip all user terminal configuration intentionally. Omit --launch (or add --dry-run) and a

This is an excerpt. Refer to the complete source and its current requirements.