[FEATURE] Ask Mode like in Cursor

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Add an “Ask mode” to similar to Cursor

Right now, the plugin forces users to choose between “Edit automatically” and “Ask before edits.” That misses an important use case: sometimes I want to ask questions about code, architecture, or correctness with no edit intent at all.

In “Edit automatically” mode especially, the plugin can misread a question as a request for changes and start editing files without explicit permission. That is risky and frustrating. A question, critique, or request for analysis should not be treated as consent to modify code.

Requested behavior

Add a fourth option:

Ask mode

The assistant can read project context and answer questions
The assistant must not edit files
The assistant must not propose or apply changes directly
Any code modifications should require switching to an edit-enabled mode

Why this matters
Prevents unwanted file changes
Makes question-asking safer and more predictable
Better separates discussion from execution
Matches a workflow many developers already expect from tools like Cursor
Current problem

The current two-mode setup mixes together different intents:

I want answers only
I want suggested edits, but with confirmation
I want automatic edits

Those are not the same thing, and the plugin should treat them separately.

Proposed Solution

Suggested outcome

A dedicated Ask mode would make the plugin more trustworthy, especially when reviewing code, debugging, or exploring ideas.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_