Support relative paths for Python/Node.js executables in portable mode

[Copilot]

Flow Launcher required absolute paths for Python and Node.js executables, breaking portability when the application is moved. Embedded runtimes within the portable directory structure were not supported.

Implementation

Core utilities (Constant.cs):

• ResolveAbsolutePath(): Resolves relative paths to absolute at runtime, based on ProgramDirectory
• ConvertToRelativePathIfPossible(): Auto-converts absolute paths within ProgramDirectory to relative format for storage

Plugin environment (AbstractPluginEnvironment.cs):

• Path resolution integrated at file existence checks and plugin instantiation
• File dialog selections automatically converted to relative paths when applicable
• Backward compatible - existing absolute paths unchanged

UI (SettingsPaneGeneral.xaml):

• Added path format descriptions with examples

Usage

Users can now configure:

Python Path: .\runtimes\python\pythonw.exe
Node.js Path: .\runtimes\nodejs\node.exe

Paths are stored as-entered (relative or absolute), resolved to absolute only at execution. File picker selections within ProgramDirectory are automatically stored as relative paths.

Enables truly portable setups with embedded runtimes that survive directory moves, USB installations, and restricted environments.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support for Relative Path for Portable Version</issue_title>
<issue_description>## Is your feature request related to a problem? Please describe.

Flow Launcher currently requires absolute paths to execute binaries such as Python and Node.js. This creates issues when using the portable version, since paths change depending on where Flow Launcher is extracted or moved.
As a result, it is not possible to fully use Flow Launcher in a portable way with embedded runtimes, limiting its usability in portable setups, restricted corporate environments, or isolated systems.

Describe the solution you'd like

I would like Flow Launcher to support relative paths, allowing:

• Executables to be defined using paths relative to the Flow Launcher root directory
• Running embedded Python and Node.js runtimes directly from the portable folder

Comments on the Issue (you are @copilot in this section)

• Fixes Support for Relative Path for Portable Version #4228

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[gitstream-cm]

🥷 Code experts: Jack251970

Jack251970 has most 👩‍💻 activity in the files.
Jack251970 has most 🧠 knowledge in the files.

See details

Flow.Launcher.Core/ExternalPlugins/Environments/AbstractPluginEnvironment.cs

Activity based on git-commit:

	Jack251970
JAN
DEC
NOV
OCT
SEP	17 additions & 28 deletions
AUG

Knowledge based on git-blame:
Jack251970: 100%

Flow.Launcher.Infrastructure/UserSettings/DataLocation.cs

Activity based on git-commit:

	Jack251970
JAN
DEC
NOV
OCT
SEP	29 additions & 27 deletions
AUG

Knowledge based on git-blame:
Jack251970: 100%

✨ Comment /gs review for LinearB AI review. Learn how to automate it here.