Two questions we have documented but not measured. Both decide whether a first-time install works, so they matter more than anything else on the wishlist.
1. Which app does the permission belong to?
macOS attributes Accessibility and Screen Recording to the responsible process. Launched from a terminal that is usually the terminal. Launched by an MCP client over npx, it may be the client.
Our README said both things in two different places until today. Neither was measured.
2. Does upgrading silently revoke it?
The helper binary is ad-hoc signed, which means its code identity changes with every build. Measured:
before rebuild: CDHash=9159173b0b30afca6c6f6084480fa68c6a831c83
after rebuild: CDHash=8c0a6b0b8e2c19ae05a6ce4e669eabcbae49d797
If macOS keys the grant to the helper rather than to the host app, then every version bump silently revokes the user's permission and the tool stops working with no obvious cause. If it keys to the host app, this does not matter at all. We do not know which.
How to measure it (about an hour, no cost)
# 1. clean install, outside the repo
cd mcp-server && npm pack
mkdir /tmp/cleanrun && cd /tmp/cleanrun
npm i /path/to/agent360-computer-mcp-0.1.0.tgz
# 2. reset the permissions for your MCP client
tccutil reset Accessibility <client-bundle-id>
tccutil reset ScreenCapture <client-bundle-id>
# 3. point the client at /tmp/cleanrun/node_modules/.bin/computer-mcp
# and write down WHICH APP the system dialog names
# 4. rebuild the helper (new cdhash), run again without touching System Settings.
# Does it still work?
Step 3 settles question 1. Step 4 settles question 2.
If you run this on your own machine, please say what you saw - even a one-line answer closes a gap we cannot close from here. If the answer to 2 is bad, it needs fixing before the package goes to npm.
Two questions we have documented but not measured. Both decide whether a first-time install works, so they matter more than anything else on the wishlist.
1. Which app does the permission belong to?
macOS attributes Accessibility and Screen Recording to the responsible process. Launched from a terminal that is usually the terminal. Launched by an MCP client over
npx, it may be the client.Our README said both things in two different places until today. Neither was measured.
2. Does upgrading silently revoke it?
The helper binary is ad-hoc signed, which means its code identity changes with every build. Measured:
If macOS keys the grant to the helper rather than to the host app, then every version bump silently revokes the user's permission and the tool stops working with no obvious cause. If it keys to the host app, this does not matter at all. We do not know which.
How to measure it (about an hour, no cost)
Step 3 settles question 1. Step 4 settles question 2.
If you run this on your own machine, please say what you saw - even a one-line answer closes a gap we cannot close from here. If the answer to 2 is bad, it needs fixing before the package goes to npm.