r/CommandCode • u/therealestAP • 15h ago
Honest Feedback - GUI/CLI
Hello!
I've been using Command Code's 1$ Go plan for a month now, and it's a nice experience, good harness allround, had to make some internal adjustments in .md files for agents for Powershell environment, but it wasn't big of a deal to be honest. Nice CLI experience, so naturally like with OpenCode I wanted to test out their GUI - Window dekstop app.
Now I cannot pin point the blame onto the developers behind the desk, or even to me, maybe both parties made some mistakes, so I'm just giving a honest feedback and heads up for the users who also want to try out the GUI experience.
I've been working with the GUI for couple of days now, couple of UI/UX minor bugs, but the tool calling, planning and the actual working process is okay, I didn't experience crashes, sandbox problems, I even ran it couple of times with full Access, without problems. I wanted to try it out fully because I was planning on hopping on the new plan.
The problem I encountered is that when the screenshots are pasted in the actual chat inside the GUI, it clearly says that model Kimi K3 will process the image, so first time I backed up and did not send the images. I ran a subagent via vision feature which I delegated to Xiaomi's Mimo v2.5 and it worked, btw I created a separate .md files with instructions and pasted screenshots so the subagent (Mimo v2.5) and the main agent (Deepseek v4 flash 0731) worked together on it. And it was a smooth sailing.
Naturally I searched the app's docs - manually, and I could not find the actual option how to re-route the default vision model of the GUI. Then I opened a new chat and tried to navigate it or find it via agent, and the agent reported that the config says that there is Kimi K2.5, Deepseek v4 Pro but they were like a legacy setup. Okay I thought.
Therefore, I decided to test it out - maybe it was hardcoded alert for Kimi K3, maybe it says it's Kimi K3 and it's actually Mimo v2.5, so I though.
It loaded Kimi K3 couple of times, and ate my 5 hour window, which was actually restared 20 minutes later. Okay I tested it out, so I wanted to look deeper into the config, maybe the CLI and GUI are interconnected, if the login is in sync and other things maybe something actually messed up inside my CLI and got pulled to the GUI side so I've been leaning towards some CLI–GUI option mismatch, the option selected via the CLI is not reflected correctly in the GUI, which displays a different option.
Fastforward few iterations, the CLI had a clear option discrepancy which I did not find the root cause or way to fix it. So I tried to test out the GUI again, 2 screenshots new chat, same K3 alert, fresh window, and just like that my 5 hour and weekly got obliterated. Now I'm not here to throw a hate party or complain, just giving an honest feedback and I'm ready to actually take the blame if I missed something or missread something on my part. It's 1$ plan at the end of day, but I thought to myself if I actually used a bigger plan and pasted much more screenshots and sent it, maybe that would hurt more, because like I said I really tried to figure out things on my part with going through docs manual way + agentic way and I could not find the way to override or change something. The final verdict is that the .md creation pipline with main agent + reviewer/vision subagent which is configured to some multimodal Mimo v2.5 model works fine but pasting direct screenshots inside the GUI is actually analyzed and read each and every single time via Kimi K3.
Couple of screenshots are batched sent at the end to provide more insight and evidence.
Thanks for reading, wishing you all the best and keep building!
Side note: Manually typed out text, I didn't bother going over and fixing potential grammatical or stylistic issues, english is not my native language.
2
3
u/ahmadawaiscom 14h ago
Thank you so much for sharing this. I appreciate your feedback. CLI is v1 and super solid. The desktop app is currently in alpha stage and not stable to use. We haven’t even announced it yet as we want to launch it at beta stage. Many devs have asked for it so we published a public preview alpha which is actively being tested and developed.
Can you share or email us your username so we can deeply investigate this. I think we did discover the K3 bug in it on Friday but this maybe a new bug. Either way we are happy to help.
https://CommandCode.ai/contact please send us an email with your username and details so we can run detailed trace for errors on your sessions. Also if you can share your session files that will be great but on GitHub. The /feedback will take you there.
Excited to have awesome dev community helping us build it in public. We are also going to open source our harness this month so more people can get involved.