Problem
RTK works when OpenCode is started from a terminal, but it does not work when using OpenCode Desktop launched normally.
This suggests the OpenCode Desktop runtime may not be loading the same environment as the user’s shell session. As a result, the RTK OpenCode plugin may fail to detect or execute the rtk binary even though RTK is installed and available in the terminal.
Expected Behavior
OpenCode Desktop should load the RTK plugin.
Actual Behavior
- Starting OpenCode from terminal: RTK works.
- Starting OpenCode Desktop normally: RTK does not appear to run.
Possible Cause
The Desktop app may be running with a different environment than the user’s login shell, especially a different PATH. The RTK plugin currently depends on resolving rtk from the runtime environment, so it may disable itself if the binary is not discoverable there.
Reproduction
- Install and configure RTK for OpenCode.
- Confirm RTK works when OpenCode is launched from terminal.
- Launch OpenCode Desktop normally.
- Run a command that should be rewritten by RTK.
- Observe that RTK is not used.
Problem
RTK works when OpenCode is started from a terminal, but it does not work when using OpenCode Desktop launched normally.
This suggests the OpenCode Desktop runtime may not be loading the same environment as the user’s shell session. As a result, the RTK OpenCode plugin may fail to detect or execute the
rtkbinary even though RTK is installed and available in the terminal.Expected Behavior
OpenCode Desktop should load the RTK plugin.
Actual Behavior
Possible Cause
The Desktop app may be running with a different environment than the user’s login shell, especially a different
PATH. The RTK plugin currently depends on resolvingrtkfrom the runtime environment, so it may disable itself if the binary is not discoverable there.Reproduction