Hook doesn't work on opencode.

[pegasusearl]

I'm using OpenCode Desktop and opencode-tui on Windows 11 natively. This happened on both versions.

Did I do it wrong?
I already installed rtk, already ran rtk init -g --opencode and rtk.ts already in the opencode plugin directory. I also already tried running rtk manually:

❯ rtk git status
* main...origin/main
 M singleton/online.gd
 M singleton/trivia.gd

I already restarted opencode after running rtk init,
But rtk still doesn't work on opencode.

The output is still very long.

It will only work if I ask the agent to use rtk.

But I thought installing rtk on opencode meant I don't have to do that. Did I misunderstand something?

UPDATE

Searching on issues tracker, it seems like it's a bug.

rtk.ts that I grabbed from this PR also didn't work, but I only grabbed the rtk.ts instead of using rtk init.

I went to try to debug it with gemini (I have no experience with javascript ecosystem), we ran many modified rtk.ts and he comes into conclusion that it might be opencode bug. As it ran rtk just fine but it's output is not compacted.

Click here to see the final `rtk.ts` and debug log

import type { Plugin } from "@opencode-ai/plugin"
import { appendFileSync } from "node:fs"

function debugLog(message: string) {
  try { appendFileSync("C:\\Users\\komi\\rtk-debug.log", `[${new Date().toISOString()}] ${message}\n`); } catch (e) {}
}

export const RtkOpenCodePlugin: Plugin = async ({ $ }) => {
  debugLog("--- PLUGIN INITIALIZING (Bun Shell) ---");

  return {
    "tool.execute.before": async (input, output) => {
      const tool = String(input?.tool ?? "").toLowerCase();
      if (tool !== "bash" && tool !== "shell" && tool !== "powershell" && tool !== "cmd") return;

      const args = output?.args as Record<string, unknown> | undefined;
      if (!args || typeof args.command !== "string") return;

      const command = args.command;

      try {
        // Use Bun's native async $ shell wrapper with .nothrow() to capture Code 3 safely
        const result = await $`rtk rewrite ${command}`.quiet().nothrow();
        const stdout = result.stdout.toString().trim();
        const exitCode = result.exitCode;

        if ((exitCode === 0 || exitCode === 3) && stdout && stdout !== command) {
          args.command = stdout;
          debugLog(`Bun Rewrite Success (Code ${exitCode}): ${stdout}`);
        }
      } catch (error: any) {
        debugLog(`Bun Shell Error: ${error?.message}`);
      }
    },
  }
}

export default RtkOpenCodePlugin

debug log:

[2026-08-27T00:25:50.624Z] --- PLUGIN INITIALIZING (Bun Shell) ---
[2026-08-27T00:26:04.669Z] --- PLUGIN INITIALIZING (Bun Shell) ---
[2026-08-27T00:26:16.758Z] Bun Rewrite Success (Code 3): rtk git status

BUT!! when I asked it the second time and feeding it with original rtk.ts, it now blames rtk instead of opencode:

Why did it stay long? Because RTK itself deliberately disables its text compaction when it notices it's running inside a non-interactive background process like OpenCode. Link to Github issue

Full conversation: https://share.gemini.google/BoaESkWMOrYP

[pradipNP]

You did not misread the installer. Two different things are going on, and Gemini bounced between them because both are real.

1. The hook rewriting git status → rtk git status is working

Your debug log already shows that:

Bun Rewrite Success (Code 3): rtk git status

Exit code 3 is RTK's "I rewrote this" status. So OpenCode is calling the plugin, and rtk rewrite is swapping the command. The part that is not happening is compaction of rtk's own output once that rewritten command runs.

Installing the plugin was never "RTK silently wraps every tool so the model sees a short summary." It only rewrites the shell command. The model still sees whatever stdout that command prints. If rtk git status dumps a long log in a non-TTY, the agent still gets the long log — which matches "it will only work if I ask the agent to use rtk" (you are then talking to a compacting code path) versus automatic bash (rewrite happens, compaction does not).

That is the #1282 behaviour: RTK disables text compaction when it thinks it is a non-interactive background process. OpenCode's bash tool is exactly that.

2. On Windows / OpenCode Desktop the stock plugin is still fragile

You are on Windows 11 + OpenCode Desktop. The generated rtk.ts uses Bun's $ and which. That is #3326:

• Desktop plugins run under Node, not Bun → $ is not a function on stock rtk init output
• Windows has no which

Your modified plugin avoided that by using $ from the Plugin context and .nothrow(), which is why rewrite started working. Stock rtk init -g --opencode can still silently no-op on Desktop.

Practical Windows plugin body (no $, no which):

import type { Plugin } from "@opencode-ai/plugin"
import { execFile } from "node:child_process"
import { promisify } from "node:util"
const execFileAsync = promisify(execFile)

export const RtkOpenCodePlugin: Plugin = async () => {
  return {
    "tool.execute.before": async (input, output) => {
      const tool = String(input?.tool ?? "").toLowerCase()
      if (!["bash", "shell", "powershell", "cmd"].includes(tool)) return
      const args = output?.args as Record<string, unknown> | undefined
      if (!args || typeof args.command !== "string") return

      try {
        const { stdout } = await execFileAsync("rtk", ["rewrite", args.command], {
          windowsHide: true,
        }).catch((err: any) => ({ stdout: err.stdout ?? "" }))
        const next = String(stdout).trim()
        if (next && next !== args.command) args.command = next
      } catch {}
    },
  }
}
export default RtkOpenCodePlugin

export default is required (#2516). Put rtk on PATH for the Desktop process (GUI apps do not inherit your terminal PATH). A user-level install of rtk, or setting the full path in the plugin, is what actually fixes "Desktop never sees rtk".

What to expect after that

• Auto bash: command becomes rtk git status (rewrite works).
• Output length: still long until RTK compacting in non-TTY is fixed or you pass whatever flag that issue settles on (--force-tty / RTK_FORCE_COLOR — check Silent output corruption when stdout is piped or redirected (suggest isatty passthrough) #1282 for the current name).
• Asking the agent to "use rtk" works because that path is interactive-ish from RTK's point of view.

So: you understood the installer as "hooks mean I never think about rtk." Today it only means "hooks rewrite the command." Compaction is a separate RTK-in-OpenCode bug, not something you missed in rtk init.