rtk-ai / rtk-ai/rtk

Set path to opencode installation

Open
#692 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:cli enhancement help wanted priority:low
Dominant language
Rust
Stars
81.1k
Forks
5.1k
Avg merge
4d 21h
Merged PRs (30d)
35

Description

I use opencode with bubblewrap like this:

❯ npm install --prefix ~/opencode/ -g opencode-ai@latest
❯ cat ~/bin/opencode.sh
#!/usr/bin/env bash
set -euo pipefail

mkdir -p $HOME/opencode/home

echo "nameserver 9.9.9.9" > $HOME/opencode/resolv.conf
echo "PWD: $(pwd)"

# XXX vnode on my box
bwrap --ro-bind /usr /usr \
      --dir /tmp \
      --dir /var \
      --symlink ../tmp var/tmp \
      --proc /proc \
      --dev /dev \
      --symlink usr/lib /lib \
      --symlink usr/lib64 /lib64 \
      --symlink usr/bin /bin \
      --symlink usr/sbin /sbin \
      --unshare-all \
      --share-net \
      --die-with-parent \
      --new-session \
      --dir /run/user/$(id -u) \
      --setenv XDG_RUNTIME_DIR "/run/user/`id -u`" \
      --setenv PS1 "bwrap$ " \
      --ro-bind /opt/vnode/bin /opt/vnode/bin \
      --ro-bind $HOME/opencode/resolv.conf /etc/resolv.conf \
      --ro-bind /etc/hosts /etc/hosts \
      --ro-bind /etc/nsswitch.conf /etc/nsswitch.conf \
      --ro-bind /etc/passwd /etc/passwd \
      --ro-bind /etc/group /etc/group \
      --ro-bind /etc/localtime /etc/localtime \
      --ro-bind /etc/ssl /etc/ssl \
      --ro-bind-try /etc/ca-certificates /etc/ca-certificates \
      --bind $HOME/opencode/home $HOME \
      --ro-bind $HOME/opencode $HOME/opencode \
      --ro-bind $HOME/.local $HOME/host/.local \
      --setenv HOME $HOME \
      --setenv PATH $HOME/opencode/bin:$HOME/host/.local/bin:/opt/vnode/bin:$PATH \
      --bind $(pwd) /work \
      --chdir /work \
      opencode $@

now i just found rtk but how can i specify where rtk init -g --opencode installs the plugin?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the CLI entry point for rtk init -g --opencode and trace how the plugin destination is selected. Define and document a way to choose an installation path, then verify that the command places the OpenCode plugin there; no specific source files or tests are mentioned in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.