Lack of Key Features #1158

Using Pi ACP, for most of this, here are some features most programs have, which Codeg lacks:

• Submitting a message, then stopping it, doesn't allow for an edit or rewind on the message. Sometimes I submit something, then realize I forgot to add something important, so I go back and edit or rewind the message chain, then restart it from that point. Can't do that, here. Just have to re-submit the entire modified message. This is especially a problem, when a model does a large amount of butchery, and it's useful to revert the diffs back to the previous message. Can't to that, here. Really need this feature. Extremely important.
• Compaction doesn't print the right number value, when finished, until a new message is submitted. Sometimes, it doesn't change, at-all, making it unclear where the token context sits, at-times. It may refresh, once a new report is received. Not sure.
• OpenCode requires a login, instead of just using the Open-Source variant, and tying my own keys, like it does when you use the GUI/TUI, etc.
• Pi is not listed as an ACP option in MCP setting tab. I had to add some MCP at PATH, for it.
• I can't pin models, in the model selection dropdown, so everytime I wanna switch models, I have to type. (pain)
• Inadequate Workspace Features. If I set a larger folder, it can't drilldown, and view the .git spots, correctly. It always just looks right at the folder you select. It makes managing multiple projects a pain. Yes, there's an additional file view feature, but it always warns me my drive isn't formatted properly for it, and it can't look at anything higher-up, or read-only, or within its own file chain, only sideways views, basically. I had to install a special read-only MCP, just to handle this issue. It's a very big problem, though, for some projects, which need to handle media files locally. Not that it can't do it, but it doesn't allow proper repo views/connections, when it's handled, that way. This is a major issue.
• No que or steering capability Ui options. Queuing is especially important, and it's a drag that I see no options for it. Hitting "enter" will queue it, but usually, there are Ui features, which also double to show hot-keys.

WORST OF ALL:

I just got hit with a $50 bill, then an hour later, another one, and could tell something was clearly wrong. In one of my threads, I sent DeepSeek Flash to fix some issues, then commit/push, and as it was doing that, I typed a follow-up for the queue, and switched the bar to Kimi K3.1 Pro, but did NOT queue. Little did I know that switching that model would actually change the assigned worker, and doing that, right there, caused a glitch, which sent Kimi into 600 recursive/looped commands, which failed repeatedly. Just cost me $100, for nothing. Lack of guardrails against numerous failed responses. Major issue.