Short answer: click Allow in the Mira chat panel and Mira continues. These prompts come from Mira itself. They are not Windows administrator prompts, and they have nothing to do with installing the Pirros plugin. You do not need admin rights on your computer, and you do not need to contact your IT team or a Pirros administrator to approve one.
Mira works by calling tools — small named actions like reading your selection, listing sheets, saving the document, or writing a new dynamic tool. Anything that only reads your model runs silently. Anything that changes something asks you first. That prompt is the permission system working as designed.
The three permission levels
Level | What happens |
Allow | The tool runs without prompting. |
Ask | Mira prompts you before every single run. |
Deny | The tool is blocked entirely. Mira will tell you it can't do that and suggest another route. |
Read-only tools default to Allow. Reading the active document, listing views, sheets, levels, families or categories, inspecting your selection, searching elements, checking model warnings — all silent.
Tools that change something default to Ask. Opening, closing or saving a document; loading a family; changing your selection; creating or deleting a custom skill; scanning folders for Revit files; and creating or deleting a dynamic tool.
What CreateDynamicTool is
Sometimes the fastest way for Mira to do what you asked is to write a small purpose-built program rather than string together dozens of generic steps. CreateDynamicTool is how it does that: Mira writes C# source, compiles it, and loads it as a new tool it can then call by name.
This is genuinely useful — it's how Mira handles bulk and one-off operations that no built-in tool covers. It is also the single most powerful thing Mira can do, because it means running new code inside your Revit session.
CreateDynamicTool asks every time — on purpose, and it cannot be set to "always allow." There is no "don't ask me again" for this one. Because it compiles and runs new code, Mira deliberately refuses to let it be switched to Allow, individually or through a blanket "allow everything." If you approved it permanently on an older build, that setting is no longer honoured and it will ask you again. The only two states available are Ask (the default) and Deny.
So a repeat prompt is not a bug, and it is not a sign that something failed to save. It's the guardrail.
How to respond to a prompt
Read what Mira says it's about to do. For a dynamic tool, that includes what the tool is for.
Click Allow to let it proceed, or Deny to stop it.
If you deny, tell Mira what you'd prefer instead — it will usually find another way.
Nothing about this step requires elevated Windows privileges. If clicking Allow appears to do nothing, that's a bug worth reporting — not a permissions problem on your machine. See Getting help below.
Change a tool's permission
Mira keeps a full table of every tool it has, with the level currently applied to each.
In the Mira chat panel, open Settings.
Go to Tool permissions.
Find the tool by name. Each row shows its category (Read, Write / Modify, or Other), its default, and its current level.
Set it to Allow, Ask, or Deny. Changes save immediately.
Two groups can't be moved to Allow, however you set them:
CreateDynamicTool — arbitrary code execution, covered above.
Folder scanning (scanning or listing Revit files in a folder) — these can walk arbitrary folders on your machine, so they always ask.
Both can still be set to Deny if you'd rather Mira never do them at all.
File access works differently
Reading and writing files is gated by folder, not by tool. Mira's own working folders — skills, tools, and temp — are always allowed, so ordinary work is silent. The first time Mira needs a folder it hasn't used before, you'll get a prompt with three options: Allow once, Always allow that folder, or Deny.
Once you've granted a folder, Mira won't ask about it again.
Frequently Asked Questions
Q: Do I need administrator rights on my computer to approve a Mira prompt?
A: No. Mira's permission prompts are part of the Mira chat panel. They are not Windows User Account Control prompts and they don't involve your machine's admin rights, your IT team, or your firm's Pirros administrator. Just click Allow.
Q: Is this related to Pirros roles and permissions?
A: No — different thing entirely. Pirros roles and permissions control what people in your firm can do with your firm's detail and family library. Mira's tool permissions control what Mira may do on your own machine, and they are set per person in Mira's own Settings. Mira has no admin role and no firm-level permission model.
Q: Why does Mira keep asking me the same thing?
A: If it's CreateDynamicTool or a folder scan, that's by design — they always ask. For any other tool, set it to Allow in Settings → Tool permissions and it will stop.
Q: Can I turn off code execution completely?
A: Yes — set CreateDynamicTool to Deny in Settings → Tool permissions. Mira will then never compile or load a dynamic tool, and will solve tasks with its built-in tools instead.
Q: Is a dynamic tool the same as a Dynamo script?
A: No. A dynamic tool is C# that Mira writes and compiles at the moment it's needed. It isn't a Dynamo graph and doesn't require Dynamo.
Q: Where are my permission settings stored?
A: In your own Windows user profile, under %APPDATA%\PirrosChatbot\. They're per person and per machine — they don't sync between computers and aren't shared across your firm.
Q: Is a denied tool permanent?
A: No. Change it back to Ask (or Allow, where allowed) in Settings → Tool permissions at any time.
Getting help
If a prompt won't accept your answer, doesn't appear when you'd expect one, or Mira reports a permission error you can't resolve from Settings, use the chat icon inside Mira or email [email protected]. Tell us the tool name from the prompt and your Revit version.
]]>