tight nest
Autodetection does not work as often as it does - why on earth did you take a way the agent mode toggle icon? The KB override shortcut does not work- we're not all having anglo kb layouts you know.
Also, how come when the above happens, my prompt ends up in context block and I can not edit it and resubmit?
You really know how to add insult to injury. Gonna cancel my subscription unless this is fixed.
spiral thicketBOT
Hi @tight nest. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
You’re right that the recent changes around agent mode and auto‑detection have been disruptive, and some of what you’re seeing is a direct consequence of those changes.
Here’s what I can tell you based on the docs and issues:
Warp’s auto‑detection tries to guess whether input is shell vs. natural language, and it does misclassify in some cases (e.g. “yes” being treated as a shell command, or text prompts being run line‑by‑line as commands). This is a known pain point for users. [Answer misclassified]
You can turn auto‑detection off so Warp stops guessing:
Settings > AI > Input > Natural Language Detection (or Settings > AI > Input Auto-detection) and disable it. [Auto-detection settings; Disabling auto-detection]With auto‑detection off, Warp will only switch modes when you explicitly do it (see below).
The old inline icons for switching between shell and agent have changed, and several users have complained about this and about the new flow. [Interface complaints] The docs still mention an “Agent icon in the input switcher” for legacy Universal Input, but they don’t clearly document the new UI state, so I can’t give you a precise “click here” path for the current build. [Entering agent mode]
Because of that, the reliable way the docs and maintainers point to now is keyboard shortcuts rather than the icon.
Officially, the override shortcut to switch between shell and agent is:
⌘ICtrl+I [Agent modality shortcuts; Universal input; Disabling auto-detection]This is not layout‑dependent (it’s the “I” key, not |), and Warp team members have explicitly confirmed that CMD‑I / CTRL‑I is the recommended way to toggle agent mode when the UI button is broken or missing. [Classic agents button bug; Agent mode shortcut clarification]
However, there was at least one bug where the UI incorrectly showed Ctrl+| on Linux, and that combination didn’t work at all. [Broken Ctrl+|] The docs don’t say how this behaves on non‑US layouts, so I can’t confirm whether your layout is part of the problem; I only know the intended binding is Ctrl+I.
If Ctrl+I / ⌘I truly does nothing for you, that’s outside what the docs cover; the GitHub issues suggest trying a different binding via Settings > Keybindings, but I don’t have step‑by‑step for remapping this specific action in the current UI. [Agent modality shortcuts]
The knowledge sources don’t explicitly describe the behavior you’re seeing (prompt going into a context block that you can’t edit and resubmit). The closest related behavior is:
But the docs don’t clearly state whether or how you can edit that original input once it’s turned into a conversation/context block, so I can’t give you a documented way to “pull it back” and re‑submit.
Based on what is documented:
Disable auto‑detection so Warp stops guessing and you control the mode:
Settings > AI > Input > Natural Language Detection → turn it off. [Auto-detection settings; Disabling auto-detection]Use explicit mode switching:
⌘ICtrl+I [Agent modality shortcuts; Universal input]If Ctrl+I / ⌘I is conflicting or not working, the docs say you can customize keybindings in Settings > Keybindings, but they don’t show the exact entry name for “override auto‑detection / switch shell ↔ agent,” so I can’t walk you through that precisely. [Agent modality shortcuts]
tight nest
Oh god please this is a dev tool. What do you think people see when you give them a sans-serif big "I" , an i char or a pipe? 🤦♂️ .
Thanks for the info though.