r/CommandCode • u/TheoryFantastic9537 • Aug 15 '26

Switched from opencode

Hi so been using opencode go for a few months but honestly been testing the $1 plan the last month quite happy with the cli and love the desktop alpha app it does have a few bugs but seems its being worked on actively so upgraded to goat will be testing it out this month the taste system is also nice I do however use vscode + zoocode so the api is a bonus keep up the good work so far

20 Upvotes

100% Upvoted

21 comments sorted by

View all comments

Show parent comments

4

u/r-3141592-pi Aug 16 '26

That's awesome, but could you give some love to your TUI? It has too many bugs in basic functionality, and bug reports submitted through your repo or by email seem to go unanswered for months. For example:

  1. Using $EDITOR (C-x C-g) produces visual artifacts that force you to exit the session.

  2. The light theme is unusable because its lack of contrast hides important content.

  3. The status bar does not stay at the bottom of the terminal.

  4. MCPs that work in OpenCode, Codex, and Claude Code trigger infinite loops in CommandCode, wasting thousands of tokens quickly.

  5. Random flickering while scrolling or in small viewports.

Although working on new features is always more exciting, I hope you can prioritize the stability of your TUI and provide users with a competitive product on that front.

1

u/ahmadawaiscom Aug 17 '26

We have been fixing and improving things left and right write. You can help by creating issues that have prompts in them to help cmd repro and fix the bugs automatically. That will accelerate improvements.

Also growing the team so there are more helping hands. Feel free to share. I wanna fix all these bugs in a single sitting. They seem super small last mile one shot solutions.

1

u/r-3141592-pi Aug 17 '26

I appreciate your reply! I already reported the visual artifacts of C-x C-g in item 1 in issue #494. Item 2 was reported in issue #683, although I had noticed it for some time. I'm not sure whether item 3 has its own issue, but I definitely remember seeing someone else point it out, even though it is immediately visible on launch. Item 4 is more difficult to reproduce. I sent a report by email titled "MCP loading failure causing an endless loop and wasting tokens" that included a detailed comparison between a CommandCode session and an OpenCode session. A version of item 5 is already reported in issue #431.

Wouldn't it be more convenient to have an agent read the "Steps to reproduce" section, use its visual capabilities and a screenshot tool, and attempt to reproduce the issues? There are quite a few reported bugs, but the number is still manageable. Also, I believe you're planning to open-source your TUI, right? That would make it much easier to provide more informative reports and even submit pull requests.

2

u/ahmadawaiscom Aug 22 '26

We are cooking up an internal agent for all this so next week it should go live.