github / github/copilot-cli

No approval required for any tool execution in docker sandboxes

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

还没有人认领这个 Issue。

area:permissions
主要语言
Shell
星标
11.2k
派生
1.9k
平均合并
14 小时 16 分钟
30 天内合并 PR
6

描述

Describe the bug

In docker sandboxes, CLI does not ask me approval for any tool executions:

  • create, edit or delete a file
  • call curl GET or POST by bash
  • create instant python script and run it
  • call dotnet command for compiling

Even though /yolo show says Tool, path, and URL requests require individual approval., I have never asked approval for tool executions.

If I ran CLI on Windows outside of docker sandboxes, approvals requested correctly. CLI seems to be affected by the environment but it is not described in reference document. IMO, yolo off should work regardless of the environment.

Affected version

1.0.83

Steps to reproduce the behavior
  1. Install docker sandboxes (winget Docker.sbx) and launch copilot (sbx run copilot)
  2. /yolo off and confirm by /yolo show
  3. Ask to run any of operations above like "I want to check yolo off behavior. Try to create and delete a file, generate and run python script, and access external URL."
Expected behavior

CLI asks me approval for the tool executions.

Additional context

Environment

  • GitHub Copilot CLI in Docker Sandboxes v0.39.0 on Windows 11
  • permissions-config.json not exists
  • permissions.disableBypassPermissionsMode is disable in settings.json

Related link
https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-command-reference#restricting-the---allow-all-options

贡献指南

打开贡献指南

从这里开始

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

调研方向

在 Windows 11 上使用 sbx run copilot 通过 Docker Sandboxes v0.39.0 重现;将 /yolo off/yolo show 与直接运行 CLI 时的情况进行比较。然后结合 permissions-config.jsonsettings.json 跟踪权限处理,并在 sandbox 中列出的每项操作都请求批准时确认 fix。

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

评估

技术栈
docker, shell
领域
authorization, cli, security
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
活跃
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 发到你的邮箱

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