[FEATURE]: Rename Windows Opencode Desktop opencode.exe as opencode-desktop.exe

[pofeng]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I am a newbie to the opencode project. Thank you for the great project.

I spent some time to understand that in Windows Opencode Desktop opencode-cli.exe is the real regular opencode command line tool, not opencode.exe afterr I download opencode-windows-x64 at https://github.com/anomalyco/opencode/releases/

So in Windows Opencode Desktop, would you please consider to rename opencod.exe to opencode-desktop.exe and opencode-cli.exe to opencode.exe.

Thank you for your great project again

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Obtaining opencode-cli.exe without installing the desktop version #7617: Obtaining opencode-cli.exe without installing the desktop version - discusses confusion about the dual executable naming on Windows

Feel free to ignore if this doesn't address your specific case.

[piperubio]

This would be a very nice enhancement to improve opencode installation and usage on Windows.
If the Desktop executable were renamed to something like opencode-desktop.exe, it would allow having a single opencode-cli installation without conflicts.

Currently, installing opencode-cli and opencode-desktop results in two separate installations. This makes it confusing to manage PATH and environment variables, and it’s unclear which binary is being used.

By renaming the Desktop executable and pointing the PATH environment variable to the shared installation folder, users could:

• Use opencode as the CLI command

• Launch the Desktop app explicitly via opencode-desktop

• Avoid duplicated installations and configuration

This would significantly improve the Windows user experience

[machinekoder]

I've added a comment in the Windows discussion a few days ago basically arguing exactly the same.

[Brendonovich]

This should be fine for macOS, on Windows it'll break existing shortcuts that people have to opencode.exe - could have the installer create a hardlink for opencode.exe? Though that probably undoes the whole point of renaming to opencode-desktop.exe in the first place.
Not sure about the impact on Linux yet, but we could have a linux-specific override for now to avoid any changes there for now, though I know #9273 highlights some issues that are being caused by the current setup on Linux too.

[machinekoder]

@Brendonovich moving the cli to a separate folder and pointing the PATH there would be an easy solution that keeps the shortcuts to the desktop app working. Maybe even keep a hardlink from opencode-cli.exe to the cli/opencode.exe to keep the other setups refering to the cli working.

[dezren39]

@Brendonovich moving the cli to a separate folder and pointing the PATH there would be an easy solution that keeps the shortcuts to the desktop app working. Maybe even keep a hardlink from opencode-cli.exe to the cli/opencode.exe to keep the other setups refering to the cli working.

maybe also link opencode-desktop.exe to the desktop version and include that in path too

[jerome-benoit]

Not sure about the impact on Linux yet, but we could have a linux-specific override for now to avoid any changes there for now, though I know #9273 highlights some issues that are being caused by the current setup on Linux too.

@Brendonovich: it's not related an OS, it's related to the case sensitivity of a filesystem: macOS default install is done on APFS without case sensitivity enabled. Installing Linux on a case insensitive FS would cause the very same issue, like any other OS.

[bluelovers]

need this fix, lol

[xiaoxiangmoe]

also need this fix, lol