Repository navigation
Need help using with opencode #603
Description
brew installed <= macos
rtk -- version. <= correct version shown
rtk gain <= nothing to see yet
rtk init -g --opencode
opencode <= GPT-5.4
Request:
git status
Response:
Thinking: Running Git status
I need to check the current status of my Git repository. It seems like I should be using the bash tool for this task. By running git status, I can see which files have changed and what my current branch is. This will help me understand what's happening in my project, so let’s get that command executed! It feels important to keep track of changes to manage the code effectively.
Shows working tree status
$ rtk git status
📌 master
Thinking: Checking git status
I’m thinking about whether I should output "📌 master" because it feels a bit odd possibly due to the RTK wrapper. It might be a good idea to run a regular git status to see where things stand. Checking the status could clarify if there are any changes or issues I need to address. I wonder how this could affect my current task — it's good to keep everything organized!
Shows working tree status
$ rtk git status
📌 master
Thinking: Considering Shell Aliases
I’m thinking about possibly using shell aliases to simplify my workflow. It could be useful for commands like git status, which I often use. By creating an alias for that, I could save time and make things easier for myself. I'll have to remind myself to set that up properly to avoid any mix-ups later on. It seems like a small adjustment that could really enhance my efficiency!
Shows working tree status
$ rtk git status
📌 master
Thinking: Debugging command issues
I'm noticing that the bash tool seems to be using a wrapper called "rtk." I wanted to run the command "git status," but it looks like something might have caused it to get messed up. I accidentally sent "rtk git status." Now, I'm thinking that maybe the system automatically added "rtk." I need to run "git status" in a plain way to see if that fixes things! Simple enough, right?
Shows working tree status
$ rtk git status
📌 master
Thinking: Correcting command error
It looks like I'm mistakenly using "rtk git status," possibly due to autocompletion messing with my input. I really need to make sure I’m typing in the exact command: "git status." It's such a simple thing, but I can easily trip over small details like this. I guess it's a reminder to double-check what I'm doing before hitting enter! Let's get this sorted out.
What did i do wrong?
Activity
jonny7737 commentedon Mar 15, 2026
% rtk gain
RTK Token Savings (Global Scope)
════════════════════════════════════════════════════════════
Total commands: 4
Input tokens: 56
Output tokens: 12
Tokens saved: 44 (78.6%)
Total exec time: 87ms (avg 21ms)
Efficiency meter: ███████████████████░░░░░ 78.6%
rtk init -gfor automatic token savingsBy Command
──────────────────────────────────────────
Command Count Saved Avg% Time Impact
──────────────────────────────────────────
──────────────────────────────────────────
Savings look great. Don't understand the No hook installed warning.
pszymkowiak commentedon Mar 16, 2026
Thanks for reporting. The issue is that RTK's git status output used emojis (
📌 master) that non-Claude LLMs (like GPT) don't understand, causing retry loops.Fix in PR #638 — replaces emojis with plain text labels:
📌 master→branch: master📝 Modified:→modified:clean — nothing to commitwhen working tree is clean, so any LLM can understand the repo stateRegarding the "No hook installed" warning in
rtk gain: this checks for Claude Code's hook specifically. The OpenCode plugin uses a different mechanism, so the warning is a false positive — your setup is actually working (4 commands tracked, 78.6% savings).jonny7737 commentedon Mar 16, 2026
Thanks for the response. I understand now. You built at nice tool for Claude and I tried to use it with GPT.
After the same issue occured with pytest, i uninstalled rtk and everything works as it should now.
This is a great and much needed tool. Thanks for creating it.
fix: replace emojis with plain text in git status output (#603)
pszymkowiak commentedon Mar 16, 2026
Tested the fix (PR #638) against qwen3.5:9b and phi4:14b via Ollama:
Before (
📌 master):After (
branch: master\nclean — nothing to commit):Both models confirmed the fix resolves the confusion.
fix: replace emojis with plain text in git status output (#603) (#638)
Release v0.31.0 — develop → master (#666)
fix: replace emojis with plain text in git status output (#603) (#638)
fix: replace emojis with plain text in git status output (#603) (#638)
Release v0.31.0 — develop → master (rtk-ai#666)
Release v0.31.0 — develop → master (rtk-ai#666)
fix: replace emojis with plain text in git status output (rtk-ai#603) (…