anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[ISSUE/FEATURE]: read with permission ask requires confirm for each file separately - proposing readall built-in tool #6937

New Issue
Open
opened 2026-02-16 18:05:39 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 18:05:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @disbolog on GitHub (Jan 20, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

AI assistant may read one file at a time, but also multiple at once. If permission on read is set to ask, it requires a separate confirmation for each file, which may become tedious. Thus the proposal is to also have a readall tool, which will improve UX in interactive mode.

Thanks in advance.

Some keywords for visibility of this issue in search: read all, read-all, readAll, read many, read multiple.

Originally created by @disbolog on GitHub (Jan 20, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request AI assistant may read one file at a time, but also multiple at once. If permission on `read` is set to `ask`, it requires a separate confirmation for each file, which may become tedious. Thus the proposal is to also have a `readall` tool, which will improve UX in interactive mode. Thanks in advance. _Some keywords for visibility of this issue in search: read all, read-all, readAll, read many, read multiple._
yindo added the discussion label 2026-02-16 18:05:39 -05:00
yindo commented 2026-02-16 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 20, 2026):

This issue might be related to existing discussions on improving permission request UX. Please check these related issues:

  • #9070: YOLO Mode - Skip Permission Prompts
  • #8463: Add --dangerously-skip-permissions (aka YOLO mode)
  • #7928: Runtime Permission Mode Toggle
  • #1813: Yolo and non-Yolo mode (auto-accept)
  • #4041: Accept all behavior for bash chains
  • #3455: Make permissions dialog non-blocking and add modifier key shortcuts

These issues approach permission friction from different angles (global modes, non-blocking dialogs, runtime toggles), while your proposal specifically suggests a readall tool. You might find valuable context in these discussions for your feature request.

Feel free to ignore if your specific use case isn't covered by these alternatives.

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be related to existing discussions on improving permission request UX. Please check these related issues: - #9070: YOLO Mode - Skip Permission Prompts - #8463: Add `--dangerously-skip-permissions` (aka YOLO mode) - #7928: Runtime Permission Mode Toggle - #1813: Yolo and non-Yolo mode (auto-accept) - #4041: Accept all behavior for bash chains - #3455: Make permissions dialog non-blocking and add modifier key shortcuts These issues approach permission friction from different angles (global modes, non-blocking dialogs, runtime toggles), while your proposal specifically suggests a `readall` tool. You might find valuable context in these discussions for your feature request. Feel free to ignore if your specific use case isn't covered by these alternatives.
yindo commented 2026-02-16 18:05:39 -05:00
Author
Owner
Copy Link
Copy Source

@disbolog commented on GitHub (Feb 13, 2026):

Bump!

Neither of the issues linked by (a pretty bs) bot are related, and it also links this one to other irrelevant issues.

How hard would it be to implement?

@disbolog commented on GitHub (Feb 13, 2026): Bump! Neither of the issues linked by (a pretty bs) bot are related, and it also links this one to other irrelevant issues. How hard would it be to implement?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6937
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?