The executable is only part of the conditions
The same binary can behave differently with different arguments, working directories, or environment variables. Record the complete successful terminal invocation and the directory from which it was launched. An executable’s own directory is not the same concept as its working directory. Relative file accesses commonly use the latter. If a configuration or input file disappears under debugging, check this distinction before investigating the parser or changing the file contents. An apparently debugger-specific failure can be an ordinary launch-condition mismatch.
Arguments are an array, not a shell command
DBG Desk takes a JSON array of strings. For example, ["input file.txt", "--verbose"] represents one filename containing a space and one option. Do not put the entire terminal command into one argument. The executable has its own field. Backslashes inside JSON strings must be escaped, so a Windows path needs the JSON spelling appropriate for that string. If input is rejected, first verify array syntax and that every element is a string. Argument parsing errors occur before the target’s own logic can be investigated.
Match the working directory and environment
There is currently no separate UI for a target working directory or environment. For programs with relative resources, start the local server from an appropriate directory or pass absolute resource paths when the target supports them. File-picker and drop opening use a temporary copy of the binary; dependencies beside the original file are not copied automatically. Use Open by path when those files are needed. Also compare PATH and other required environment variables in the terminal that launched the server. Change one condition at a time.
Inspect early exit separately from a crash
A program can intentionally return an error after checking arguments or reading configuration. Read the output and exit status before calling an immediate exit a crash. Stop at main and follow argument handling and the first resource access. Interactive standard input is not provided by the current DBG Desk UI, which can also explain a waiting target. A useful report includes the argument array, starting directory, required file layout, and relevant environment conditions with secrets removed.
A short relative-path experiment
Run the same executable from two directories, then compare an absolute input path where supported. If only one starting directory finds input.txt, investigate how the program constructs that path. If it uses a fixed internal filename, changing arguments alone will not solve the issue. Once launch paths match, move on to encoding, access rights, or content handling as separate checks.