The rtk tool obfuscates identifiers

[gautaz]

Hello,

Lately, Big Pickle (free test model from opencode) started to report this:

The `rtk` tool obfuscates identifiers, making this hard to read. Let me use the Grep tool (which doesn't obfuscate) to search for references.

Which defeats the purpose of using RTK...

Is anyone experiencing this type of behavior?
Is there a workaround for such cases?

[aeppling]

Hey @gautaz , never seen this, thanks for reporting.

Agents should know how to use "rtk proxy" to bypass a command rewrite if a problem is encountered, here it should have use this instead of bypassing the bash tool.

But anyway, "rtk proxy " command is just a bypass in case of errors, we want to fix the root issue, if you have any session logs (transcript) that you could provide so we can troubleshoot and fix this, it would be nice. (warning to your sensitive data, you can reach us from here as well https://pro.rtk-ai.app/contact

So what would help us to troubleshot your problem:

• Model & Harness
• How RTK was installed (is hook setup, is the rtk context setup)
• Hook debug log (see below how to get those)
• Session transcript (keep sensitive information out)

export RTK_HOOK_AUDIT=1
rtk hook-audit              # last 7 days
rtk hook-audit --since 0    # all time
rtk hook-audit -s 1         # last day

Thanks for reporting, awaiting further information so we can debug and avoid this happening again.

[gautaz]

Hello @aeppling ,

Thanks for your guidance.
I'll try to answer your questions to the best of my abilities (expect them to be low ;-)):

Model & Harness

I am using Opencode with their default "Big Pickle" model.

How RTK was installed (is hook setup, is the rtk context setup)

Here is a link to my nix module installing opencode with rtk as a plugin.
Basically, rtk is installed as a plugin of opencode by copying it in the plugin dir of opencode (I am not sure rtk init -g --opencode is a valid option for a nix recipe, I'll need to dig further into this).

Hook debug log (see below how to get those)
Session transcript (keep sensitive information out)

I'll try these and report back as soon as possible 👍 (hopefully I should reproduce the issue next week).