By default, Sixth will ask for your permission before calling any tool, including reading or writing files.If you want to allow Sixth to do something without asking, you can set the Auto Approve permission for that tool.
Personally, I like to keep auto-editing disabled because it gives me a chance to review changes every step of the way.For most serious development workflows, I recommend starting with:
Auto-approving read access to project files
Setting a reasonable maximum request limit (10-20)
This gives Sixth enough freedom to explore your codebase without constant interruptions, while still requiring permission for edits or potentially destructive actions.As you build more trust in Sixth’s capabilities with your specific projects, you can gradually increase the permissions to match your comfort level.Remember that you can always adjust these settings as your needs change - tighten permissions for critical production work, or loosen them when prototyping and exploring.You can even use the quick “star” actions to quickly toggle your auto-approved selections on and off as you go.