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

full-auto / permissions / etc #4

New Issue
Closed
opened 2026-02-16 17:24:49 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 17:24:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @adamdotdevin on GitHub (May 15, 2025).

i hate giving permissions. i feel like this precedent was set by incumbents and it's dumb. this is what git is for? idk, maybe this is heavy handed, but i know other tools are opting out of prompting for permission and that's what i would prefer, as a user.

we could just have a full-auto option, a la codex or claude code's shift+tab (kind of); could be enabled by default?

we could also do the codex thing and use macos seatbelt to sandbox open code to your project dir (+ config dirs/etc).

opening this issue to get thoughts from others, i'd love to just rip out permissions altogether but i also hope to not be the only user of open code, soooooo.

Originally created by @adamdotdevin on GitHub (May 15, 2025). i hate giving permissions. i feel like this precedent was set by incumbents and it's dumb. this is what git is for? idk, maybe this is heavy handed, but i know other tools are opting out of prompting for permission and that's what i would prefer, as a user. we could just have a full-auto option, a la codex or claude code's shift+tab (kind of); could be enabled by default? we could also do the codex thing and use macos seatbelt to sandbox open code to your project dir (+ config dirs/etc). opening this issue to get thoughts from others, i'd love to just rip out permissions altogether but i also hope to not be the only user of open code, soooooo.
yindo closed this issue 2026-02-16 17:24:49 -05:00
yindo commented 2026-02-16 17:24:49 -05:00
Author
Owner
Copy Link
Copy Source

@indeep99 commented on GitHub (May 15, 2025):

Full auto option makes sense, but imo probably shouldnt be enabled by default, pragmatism makes sense for first time users.

On sandboxing, is this about write operations only? If both read and write, Id be concerned about it being a hard limit of the scope as there are cases where Id want to reference a file from a different project (follow this style kind of thing). In case its about both read and write, would we be able to expand scope dynamically? I am sorry if I misunderstood the second suggestion!

@indeep99 commented on GitHub (May 15, 2025): Full auto option makes sense, but imo probably shouldnt be enabled by default, pragmatism makes sense for first time users. On sandboxing, is this about write operations only? If both read and write, Id be concerned about it being a hard limit of the scope as there are cases where Id want to reference a file from a different project (follow this style kind of thing). In case its about both read and write, would we be able to expand scope dynamically? I am sorry if I misunderstood the second suggestion!
yindo commented 2026-02-16 17:24:50 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (May 15, 2025):

i'd have to look at what approach codex takes w/r/t read vs write, but my first thought was that it would be for both read and write (prevent the tool from reading sensitive system files? idk). i don't feel strongly either way.

@adamdotdevin commented on GitHub (May 15, 2025): i'd have to look at what approach codex takes w/r/t read vs write, but my first thought was that it would be for both read and write (prevent the tool from reading sensitive system files? idk). i don't feel strongly either way.
yindo commented 2026-02-16 17:24:50 -05:00
Author
Owner
Copy Link
Copy Source

@ezynda3 commented on GitHub (May 16, 2025):

Sometimes I like to scroll through individual edits before approving them (mostly to stop Claude from being too eager to please) but I also sometimes like to go YOLO mode so would love the option to configure this or toggle this on/off per project.

@ezynda3 commented on GitHub (May 16, 2025): Sometimes I like to scroll through individual edits before approving them (mostly to stop Claude from being too eager to please) but I also sometimes like to go YOLO mode so would love the option to configure this or toggle this on/off per project.
yindo commented 2026-02-16 17:24:50 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (May 16, 2025):

Every so often Claude goes wild and wants to "start from scratch" just because it confused itself, so I would like to control the permissions easily.

I only use opencode now but I used Claude Code and Codex, and I enjoyed the way Claude Code does "full auto" quite a bit. I like being able to turn it on and off super easy depending on what I prompt it to do

@rekram1-node commented on GitHub (May 16, 2025): Every so often Claude goes wild and wants to "start from scratch" just because it confused itself, so I would like to control the permissions easily. I only use opencode now but I used Claude Code and Codex, and I enjoyed the way Claude Code does "full auto" quite a bit. I like being able to turn it on and off super easy depending on what I prompt it to do
yindo commented 2026-02-16 17:24:50 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (May 16, 2025):

yeah, i think the shift+tab toggle approach is good

@adamdotdevin commented on GitHub (May 16, 2025): yeah, i think the shift+tab toggle approach is good
yindo commented 2026-02-16 17:24:50 -05:00
Author
Owner
Copy Link
Copy Source

@thdxr commented on GitHub (Jun 14, 2025):

going to close for now as 0.1.x is a rewrite. feel free to open a new issue if it's still a problem

@thdxr commented on GitHub (Jun 14, 2025): going to close for now as 0.1.x is a rewrite. feel free to open a new issue if it's still a problem
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
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#4
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?