github
When in agent mode, minimize unnecessary interruptions.
Currently, in agent mode, there are the following types of interruptions:
- If switched to another application, the agent will forcibly switch back to Xcode after modifying a piece of code.
- Seek user authorization permission.
- For example, by running a command through the terminal.
- Exceed the limit.
- The number of tool calls exceeds the maximum limit.
- Your prompts have exceeded the limit. Please open a new tab to continue.
For the first type of issue, I hope it can be improved so that after making modifications, it doesn’t switch to Xcode. That way, I can use this computer for other tasks while it’s working.
For the second category, I would like to add an additional "Agree" option so that I don't have to keep clicking "Agree" each time.
For the last category, I’d like to ask: do all models have the same restrictions? If not, could you indicate which model has a broader range? Also, if the process isn’t completed, isn’t it likely to continue automatically? Why do I need to get involved? After all, if the prompt really does reach its maximum length, you could simply prompt me to open a new tab then—it wouldn’t be too late. In my view, it’s quite easy to reach the limit anyway.
Here are my suggestions. The most important improvement I hope for is the first one, because the interference it causes is really overwhelming. If it's not improved, I can only let the computer run there, and all I can do is sit and watch, unable to do anything else. That's because it keeps switching to Xcode nonstop.
issue 1: it's because agent uses the Xcode editor to modify the file in order to support undo. If we use a less interruption way to modify disk file directly, it losses the undo. There is a tradeoff to consider here.
issue 2: we can consider exposing an auto-approve setting for this.
issue 3: they are useful feedback. it has room to optimize like popping up a button to continue or new a conversation.
issue 1: it's because agent uses the Xcode editor to modify the file in order to support undo. If we use a less interruption way to modify disk file directly, it losses the undo. There is a tradeoff to consider here.
May by using git or an MCP of git? Also, I have never use the undo. If I finally found that my idea was wrong, I used git to cancel all changes. If I found Copilot was wrong, I didn't use undo either. I just told Copilot where was wrong and asked it to fix. So the files were always kept by default.
Another request here to consider an auto-approve for issue 2. Is there a place I can upvote it?
