Option to Approve Memory-Bank File Writes Without Automatically Approving Edit Files #1401
Kayphoon
started this conversation in
2. Design improvements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Kilocode team and contributors 👋,
I really enjoy using Kilocode and appreciate the thoughtful design and automation it provides for managing code changes and memory-bank file updates.
I’d like to propose a new configuration option that would allow users to manually approve code changes, while still automatically approving writes to memory-bank files.
🚀 Proposed Feature:
Add a setting where:
Any code changes (e.g., modifications to source files) require explicit user approval
Any changes to memory-bank files are automatically approved and written
📌 Motivation:
This would be especially helpful in workflows where:
The user wants to carefully review and approve actual code changes
But memory-bank updates (e.g., logs, context, or metadata) are safe to update automatically without blocking the flow
This kind of granular control would improve usability in more complex or production-like environments, while still maintaining safety for actual code changes.
PS:This proposal was written with the help of AI, as English is not my first language. If anything is unclear or could be improved, please let me know — I'm happy to refine it!
Beta Was this translation helpful? Give feedback.
All reactions