Per-Client Revocable Identities
Each AI client can be issued an individual revocable key with its own capability profile (by default a shared launch token is used, which is not revocable in v1). Revocation takes effect on the next request.
V1 PRODUCTION CAPABILITIES
Governed Control Grounded in Reality
These capabilities run in the current macOS build, providing multi-AI coordination and governed access.
Durable Effects & Idempotency
Mutating operations require a durable idempotency key. Prevents duplicate side effects, replays recorded results, and safely handles UNCERTAIN states without blind retries.
Screen Lock
An in-memory lock for calls that pass through Mercury (screenshots, opening apps, AppleScript). A second client waits up to 3 seconds and is then refused; the first client keeps the lock for 10 seconds after its last call.
Local Operation Log (JSON Lines)
Operations write a row to the local audit.jsonl log with client, tool, allowed/denied status, duration, and result timestamp; request payloads are not stored.
Hardware & Mobile Drivers
Direct native automation on macOS host drivers, Android actions over adb, and connected iOS / iPadOS device list discovery.
Explicit-Argv Safe Execution
Commands run as an explicit argument list without a shell; access is governed by the client profile.
USE CASES
What Mercury does in practice
Practical automation workflows running through the local daemon and MCP bridge.
01
Work with project files
Ask an AI assistant to read a project folder, summarise it and write the result to a file. Give a review-only assistant a read-only token.
02
Run a build and report
Let an assistant run a program or script on your Mac with explicit arguments and read its output.
03
Use the screen
Take a screenshot, open an app or run an AppleScript. If two assistants try at once, the second waits or is refused.
04
Check a connected phone
List connected Android devices and send taps, swipes, text and key events with adb. iPhone and iPad are listed only.
05
Keep a record
Each call is written to a local operations log with the client, tool, result and time. Request contents are not stored.
Every action runs without a confirmation prompt, according to the profile you assign.
CLIENT COMPATIBILITY
MCP Clients
Tested with ChatGPT and Claude. Works with MCP clients; a sample configuration is available for Gemini.
ChatGPT Tested
Cloud sessions connect via user-configured tunnel to the local Mac daemon.
Transport: User-configured tunnel · Port 17890
Claude Tested
Local engineer CLI or desktop interface connected via standard stdio MCP bridge with designated clientId token.
Transport: Stdio Bridge · claude-code token
Other MCP clients Not tested
A sample configuration is available for Gemini.
Transport: Standard MCP Bridge