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

[FEATURE]: When using the experimental plan mode, allow opencode to write the plan without asking for permission #7182

New Issue
Open
opened 2026-02-16 18:06:24 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:06:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @svanharmelen on GitHub (Jan 22, 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

As the title mentions, it would be nice if OpenCode can write its own plan file when using the experimental plan mode. Now for each new session it asks again if it's okay for it to write the plan or update the plan file, while it's actually, in my opinion, its own plan file based on the current task.

So I think it should be allowed to write and update that (somewhat internal) file managed and used by OpenCode itself, without me having to explicitly allow access each and every time.

Originally created by @svanharmelen on GitHub (Jan 22, 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 As the title mentions, it would be nice if OpenCode can write its own plan file when using the experimental plan mode. Now for each new session it asks again if it's okay for it to write the plan or update the plan file, while it's actually, in my opinion, its own plan file based on the current task. So I think it should be allowed to write and update that (somewhat internal) file managed and used by OpenCode itself, without me having to explicitly allow access each and every time.
yindo added the discussion label 2026-02-16 18:06:24 -05:00
yindo commented 2026-02-16 18:06:24 -05:00
Author
Owner
Copy Link
Copy Source

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

This issue might be a duplicate of existing issues. Please check:

  • #7579: [FEATURE]: Save plan to file for token efficiency and compaction persistence - discusses saving plans to files for better context management and persistence across compaction events

Feel free to ignore if this doesn't address your specific case.

@github-actions[bot] commented on GitHub (Jan 22, 2026): This issue might be a duplicate of existing issues. Please check: - #7579: [FEATURE]: Save plan to file for token efficiency and compaction persistence - discusses saving plans to files for better context management and persistence across compaction events Feel free to ignore if this doesn't address your specific case.
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#7182
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?