03 Core concepts and features
Conversation permissions and file access
In a local project, choose file permissions for each Mira conversation to control how it reads and modifies materials on your computer. The control below the input shows Read only, Working directory writable, or Full access.
Choose conversation permissions
Permission | Scope | Suitable work |
|---|---|---|
Read only | Read local files. Modifying files through write or edit tools requires one-time approval. | Read materials and inspect existing data or code. |
Working directory writable | Write or edit tools can modify files inside the project's working directory. Changes outside it require one-time approval. | Generate analysis scripts, results tables, and reports within a research folder. |
Full access | Runs with the current operating-system user's permissions and can read, modify, and delete files accessible to that user. | Tasks with a confirmed scope that require work across directories. |
Click the current permission to open the menu. When selecting Full access, read the explanation of file, network, and remote-model access and tick the confirmation box to enable it.
Conversation permissions apply only to the current conversation. Wait for the current round to finish, or stop it, before changing them.
Handle an approval request
When an operation exceeds current permissions, Mira asks for confirmation in the conversation. Review the action, target file or command, working directory, and reason, then allow or deny it.
For example, if you allowed reports to be created only within the project directory but a task needs to modify a file elsewhere, you can approve that operation once, or deny it and ask Mira to save the result inside the project.
For raw experimental data, specify that originals should be retained and analysis results saved separately. This makes later revisions and checks easier.
Working directory and execution scope
The working directory is the folder selected when creating a local project, used to organize inputs, scripts, and outputs. The permission menu controls the modification scope of file tools. Command execution also depends on operating-system and user permissions, and local execution inherits the computer's network environment.
File contents and command output may be sent to the online model in use. Choose a dedicated research directory and specify which files may be processed to keep the task scope clear. On Windows, also read the local-execution notes shown when creating the project.
Permissions for other local Agents
For local Agents such as Codex and Claude Code, configure runtime permissions in Settings → Agents → the Agent's Runtime permissions. The Agent's native modes govern subsequent runs, including existing conversations. Mira's conversation-permission menu does not apply an additional layer.