Auto-Approve

Set fine-grained permissions on what you allow Byteable AI Code to do in an automated way.

The Auto Approve menu lets you control exactly what Byteable AI Code can do without asking for permission each time.

How it works

By default, Byteable AI Code will ask for your permission before calling any tool, including reading or writing files.

If you want to allow Byteable AI Code to do something without asking, you can set the Auto Approve permission for that tool.

Permission Options

Read project files

Allows Byteable AI Code to read files within your current workspace without asking

Read all files

Extends read permission to files outside your workspace (system files, config files, etc.)

Edit project files

Allows Byteable AI Code to modify files within your current workspace without confirmation

Edit all files

Extends modification permission to files outside your workspace

Execute safe commands

Allows execution of terminal commands that the model deems non-destructive

Execute all commands

Permits execution of any terminal command without asking

Use the browser

Allows Byteable AI Code to use the browser tool to fetch web content

Use MCP servers

Permits connection to and usage of MCP servers for extended functionality

Maximum requests

Sets the number of consecutive automated actions Byteable AI Code can take before requiring your input

Best Practices

Personally, I like to keep auto-editing disabled because it gives me a chance to review changes every step of the way.

Recommended Starting Configuration

For most serious development workflows, we recommend starting with:

Auto-approving read access to project files
Setting a reasonable maximum request limit (10-20)

This gives Byteable AI Code 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 Byteable AI Code'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.

Security Considerations

Safe Permissions

• Read project files
• Use the browser
• Use MCP servers (trusted)
• Execute safe commands

Use with Caution

• Edit project files
• Read all files
• Edit all files
• Execute all commands