rtk-ai/rtk

OpenCode Desktop does not detect rtk when launched from macOS GUI

Open

#2,039 opened on May 22, 2026

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (2,914 forks)batch import
area:configbughelp wantedplatform:macospriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

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

  1. Install and configure RTK for OpenCode.
  2. Confirm RTK works when OpenCode is launched from terminal.
  3. Launch OpenCode Desktop normally.
  4. Run a command that should be rewritten by RTK.
  5. Observe that RTK is not used.

Contributor guide

Research direction
Investigate how OpenCode Desktop sets its environment variables and ensure the rtk binary is found in PATH. This may involve checking how the desktop app inherits or modifies the shell environment.
Tech stack
rust
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75