When in agent mode, minimize unnecessary interruptions.

未关闭
#443 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
macos, swift
领域
ai, desktop, devtools

调研方向

未指定任何文件、测试或入口点。首先复现 agent-mode 的三种中断类型,然后追踪应用切换、授权提示和使用限制的处理方式;要视为完成,需要有经 maintainer 批准的范围,以及针对已优先处理的中断变更的明确行为。

由索引模型根据 Issue 内容生成。

描述

Currently, in agent mode, there are the following types of interruptions:

  1. If switched to another application, the agent will forcibly switch back to Xcode after modifying a piece of code.
  2. Seek user authorization permission.
    1. For example, by running a command through the terminal.
  3. Exceed the limit.
    1. The number of tool calls exceeds the maximum limit.
    2. 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.

主要语言
Swift
星标
6.3k
派生
2k
平均合并
3 天 21 小时
30 天内合并 PR
2

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/CopilotForXcode 的其他 Issue

查看 github/CopilotForXcode 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。