nucleic/nucleic
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Provisioned VM Image Preparation

Browse Source 
Nucleic-Session: 28559516-7571-4295-A21C-28B0B95D9427
Co-authored-by: Nucleic <[email protected]>
This commit is contained in:
abkslm
2026-07-07 04:06:08 -07:00
co-authored by nucleic
parent c24d0a4d07
commit 14521c2c36
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/MACOS_VM.md
+8 -2
View File
@@ -555,9 +555,15 @@ the **optional in-guest AX agent** (§12.5), both of which run inside the guest.
Accessibility (`kTCCServiceAccessibility`) for `/usr/local/bin/cliclick`, written into the system
TCC.db.
### 12.5 The TCC / SIP reality (honest)
### 12.5 The TCC / SIP reality (honest) — only for the optional AX agent
Pre-granting TCC unattended is the sharp edge, and there's no clean path:
**This section no longer applies to default computer use.** Host-side virtual IO (§12.2) needs no
guest TCC, so **SIP stays on** for the normal computer-use experience. TCC/SIP matters only when you
opt into the **semantic AX agent** (`MacVMSettings.axAgentEnabled`) — the in-guest `NucleicVMAgent`
that adds Accessibility control and drives app windows on a macOS 26 guest where the framebuffer bug
blanks them in pixel screenshots (§12.6). That agent reads/drives the guest with Apple's frameworks
*inside* the VM, so it needs the guest's TCC grants, and pre-granting them unattended is the sharp
edge with no clean path:
- The grants live in the **system** db `/Library/Application Support/com.apple.TCC/TCC.db`, which SIP
protects from writes.