Skip to content

v0.3.0 — One session grant for native app access

Latest
Latest

Choose a tag to compare

View all tags
@pgeske pgeske released this 07 Sep 04:46
v0.3.0
This tag was signed with the committer’s verified signature.
pgeske alyosha
SSH Key Fingerprint: CmedSDF5xd33mFa8x+Tou+rrzs3ODColmc8uN0aZuRI
Verified
Learn about vigilant mode.
3eb232b
This commit was signed with the committer’s verified signature.
pgeske alyosha
SSH Key Fingerprint: CmedSDF5xd33mFa8x+Tou+rrzs3ODColmc8uN0aZuRI
Verified
Learn about vigilant mode.

Session approval now also covers recognized native “Allow ChatGPT to use [app]?” prompts during app inspection.

  • Requires explicit bridge session consent, the configured Computer Use server, the known wording, empty-form schema, and persistence-option metadata.
  • Replies with session acceptance only; never asks for permanent approval.
  • Unknown formats, extra fields, non-app permissions, and requests during mutations remain forwarded or denied.
  • Stop/cancellation invalidates old callbacks. Native macOS permissions are unchanged.
  • Exact-app launch trust alone does not authorize native approvals. Consequential-action confirmation remains the calling agent's responsibility.

Validation: 38 automated tests, lint, typecheck, build, and a live Calculator test that computed 4 + 5 = 9 with a screenshot and exactly one host approval request. The test cancels any extra native prompt rather than masking it.

There is no stable upstream app-access kind field. This intentionally conservative matcher falls back to prompting if the native format changes.

npm install -g --ignore-scripts https://github.com/pgeske/mac-computer-use-mcp/releases/download/v0.3.0/pgeske-mac-computer-use-mcp-0.3.0.tgz

Restart/reload the MCP connection after updating.

Assets 4
Loading