The recent 1.16.0 update, which introduces dedicated slash commands (`/`) for Continue's core actions, represents a significant shift in user interaction. From a pure workflow efficiency standpoint, this appears to be a move towards keyboard-centric velocity, reducing dependency on mouse-driven UI elements like the sidebar or context menus.
Initial analysis suggests a potential time-saving, but it's highly dependent on user familiarity and the specific command. Consider the comparative actions:
* **Old UI:** Hover over code -> click `+` in the popup -> select "Edit" or "Generate."
* **New Slash Command:** Select code -> type `/edit` -> type instruction.
For a single, simple operation, the mouse-driven UI might still be marginally faster for some. However, the slash commands likely pull ahead in more complex, sequential workflows where the hands never leave the keyboard. The critical factor is muscle memory development.
My primary questions for the community are:
* Have you quantified any change in task completion time for common operations (e.g., inline generation, multi-step refactoring)?
* Does the reduction in visual UI clutter outweigh the cognitive load of remembering command verbs (`/edit`, `/test`, `/fix`, `/clear`)?
* Are there any commands you find yourself still using the old UI for, and why?
The true TCO of this feature isn't monetary, but in adoption friction versus long-term productivity gain. I'm interested in data-driven observations.
independent eye
Good point about complex workflows. I'm still building muscle memory, but the slash commands are a win when I'm already typing. It's less about raw speed for one task and more about keeping flow.
You mentioned cognitive load of remembering commands. That's my hangup too. I wish there was a quick overlay like Cmd+K to see all the slash options without breaking my focus. Does anyone use a cheat sheet?
Totally agree on the muscle memory thing. It's like switching from a GUI git client to the command line. At first you're slower, but eventually you can't go back because your hands never leave the keyboard.
That quick overlay idea is great. I wonder if it's a conscious design choice to avoid clutter, or just a v1.0 thing. Do you think a minimal auto-suggest, like VS Code's command palette, would work better than a full cheat sheet?