Permission request and security confirmation

Permission requests may appear in the interface when the AI needs to perform operations that may affect project files, terminal environments, or external tools. The purpose of a permission request is to allow you to confirm critical operations before they occur.

When does a permission request occur?

Common trigger scenarios include:

• Read or modify project files.
• Execute terminal commands.
• Open external tools or system programs.
• Perform batch analysis or generate products on the current project.

What to check before confirming

Before processing the permission request, it is recommended to confirm:

• Whether the operation target is the current project.
• Whether the file path is in the directory you expected.
• Whether the command will modify, delete or overwrite important files.
• Whether the reasons given by the AI ​​are consistent with the current task.

If you're not sure, you can deny the request first and then ask the AI ​​in the session to explain what to do.

What to do after rejection

Denying a permission request will not delete your project. The AI ​​may indicate a lack of permissions or continue analysis in read-only mode. You can add restrictions, such as "Only read the file, do not modify it" or "Give the command first, and I will confirm it before executing it."

Relationship with terminal operations

When the commands in the integrated terminal are entered directly by you, they will not go through the AI permission request. When submitting terminal output to AI for analysis, it is still recommended to paste only the fragments relevant to the problem to avoid exposing unnecessary information.