Orvial asks for powerful permission. You should know exactly why.

Orvial expects to use the macOS Accessibility APIs to identify and control the windows you ask it to manage — to move, resize, minimise, restore or focus them. There is no narrower macOS interface that can do this.

macOS requires you to grant this permission explicitly, and it is powerful: it lets an approved app control accessible interface elements in other applications. That is exactly why Orvial should ask for it only after explaining what it is for, rather than on first launch.

Revoking it stops window control. Orvial is being designed to notice that loss, say so plainly, and explain how to restore access — not to fail silently or keep pretending it is in control.

Normal Orvial workspace control should not require Screen Recording. If a later feature genuinely needs it, it should arrive as a separate, separately explained, optional permission.

Engine Lab — the internal test harness — may use its own observation instrumentation. Those privileges are not intended to reach the shipping application.

Not for the core product. Broad file access should not be requested for convenience, and asking for it would undercut the reason to trust a tool that already controls your desktop.

No. If a voice surface is built later, the microphone should be requested only when you explicitly turn that feature on.

Only where a real, shipping integration needs it. Permissions should not be requested in advance because a roadmap feature might one day want them.