Command Entries
Command entries let you run a local command directly from the Conduit sidebar. The output is displayed in a read-only xterm.js terminal with real-time status overlays. Useful for scripts, build tools, log tailing, and any process you want to launch with a single click.
Configuration
Each command entry is configured with the following fields:
- Command — The executable or script to run.
- Arguments — Optional arguments passed to the command.
- Working directory — The directory the command runs in. Defaults to the current user's home directory if left blank.
- Shell — The shell used to launch the command:
bash,zsh,sh,PowerShell, orcmd. Choose the shell that matches your script requirements. - Timeout — Optional maximum runtime in seconds. The process is terminated if it exceeds this limit.
Run As Mode
Command entries support two execution modes:
- Current user — The command runs as the user currently logged in to the operating system. No credential is required.
- Credential user — The command runs as a different user by selecting a credential from the vault. Useful for running scripts with elevated privileges or as a service account.
Windows cross-user execution
On Windows, cross-user execution uses CreateProcessWithLogonW to launch the process under the specified account without requiring UAC elevation prompts.
GUI Application Mode
Toggle GUI application when the command launches a graphical program rather than a terminal process. When enabled, the command is started without attaching a terminal, allowing windowed applications to open normally. The terminal pane still displays any startup output or errors the process emits before detaching.
Terminal Output
Command output is displayed in a read-only xterm.js terminal. A status overlay shows the current state of the process:
- Running — The process is active and producing output.
- Exited — The process finished. The exit code is shown in the overlay.
- Error — The process could not be started or terminated unexpectedly.
- Timeout — The process was stopped because it exceeded the configured timeout.
Controls
- Restart — Re-launches the command from the beginning, clearing previous output.
- Stop — Sends a termination signal to the running process.
Quick rerun
After a command exits or times out, use Restart to run it again without opening the entry editor.