Cursor is rolling out a set of quality-of-life updates to its terminal tool, highlighting new slash commands aimed at making agent workflows easier to manage in the CLI, according to a post from Cursor (@cursor_ai).
The headline feature is /debug, which Cursor says is designed to help “find root causes and fix tricky bugs that are hard to reproduce or understand,” alongside other additions that focus on configuration and keeping runs on track.
The new Cursor CLI commands
Cursor’s announcement focuses on four user-facing commands:
/debug: A debugging flow intended to surface root causes for difficult or hard-to-reproduce issues. Cursor positions it as a way to make terminal-based bug hunting less opaque. (link)/btw: A command for asking a side question “without derailing the agent’s current run,” essentially a lightweight interruption that’s meant to preserve momentum. (link)/config: Opens a settings panel inside the CLI for changing defaults and runtime preferences. Cursor also notes configuration can be applied using a skill called/update-cli-config. (link)/statusline: Adds customization for the CLI status bar, letting developers choose which session and runtime signals are visible. (link)
Cursor also pointed to a download link for the CLI. (link)
Early reactions: debugging first, then “undo”
Replies to the announcement centered heavily on /debug. Several developers framed it as a quality-of-life win for log-heavy terminal work: one called /debug “a start” but asked for “line-by-line diffs and context logs,” while another said it made terminal AI more appealing specifically for “server side bugs,” where the terminal is already the primary interface.
Other feedback was more about workflow safety and ergonomics. Multiple replies asked Cursor for /undo (and, separately, /revert). Another request: drag-and-drop file support to make it less painful to provide file context into an agent input window. There were also questions about whether these features work with the --mode flag, as well as comments about model availability (including requests for “kimi k2.6” to be added to the models list).
Why Cursor is emphasizing the terminal
Cursor’s framing here is notable: rather than touting broader “agent” capability, it’s shipping pragmatic CLI controls—debugging, side-questions, configuration panels, and a customizable status line. For teams that already live in terminals for production incidents, SSH sessions, and log triage, that focus lines up with where AI assistance can reduce friction without requiring a full IDE context.
At the same time, the reply thread shows the obvious follow-ups: visibility into what an agent is doing (/debug being one step), and the ability to safely roll back changes (/undo) when terminal workflows move fast.
