UseMyMac
Left: Claude Code, anywhere. Right: a Mac running usemymac up. The agent reaches it only through the printed URL.
Turn your Mac into a remote computer-use host. One command on the Mac, one paste into Claude Code or Codex, and the agent can see your screen, click, type, and open apps.
Built on CUA's computer-server for the macOS driver.
UseMyMac adds the parts that make it safe to reach from outside: a bearer token, a tool
allowlist that hides shell and filesystem access by default, a Cloudflare quick tunnel,
keep-awake, and a permissions preflight.
Quick start
uvx usemymac up
Or without uv installed:
curl -fsSL https://raw.githubusercontent.com/yunfeng-enrich/usemymac/main/install.sh | sh
Either way UseMyMac fetches cloudflared on first run and starts the server. It prints one line to paste into your agent, plus the one-line commands:
claude mcp add --transport http usemymac https://<host>/<token>/mcp
codex mcp add usemymac --url https://<host>/<token>/mcp
The token lives in the URL so no client needs custom headers. Authorization: Bearer <token>
against https://<host>/mcp works too.
Permissions
macOS grants Screen Recording and Accessibility per app, and the app is whichever
terminal launched usemymac. The first run triggers both prompts. Screen Recording only
takes effect after that terminal is fully quit and reopened. Without it, screenshots
are black and window titles are empty. Check with:
usemymac check
What is exposed
By default: screenshot, mouse, keyboard, clipboard, windows, app launch, and the accessibility tree. Not exposed unless you ask:
--allow-shelladdscomputer_run_command--allow-filesadds file read, write, and delete tools
Other flags: --no-tunnel for LAN or SSH-forwarded use, --width/--height to scale
screenshots and coordinates for the model, --port, --token.
Security
This is your real desktop on a public URL. The token is the only lock, and it is in the
URL, so treat the URL like a password. Both the hostname and the token are new on every
run, so a leaked URL stops working the moment you Ctrl-C. Keep the terminal visible while
an agent is connected. Pass --token only if you need a fixed one.
Status
Spike. Works end to end on macOS 15 with Claude Code over a Cloudflare tunnel. Not yet: signed menu bar app, persistent tunnel hostnames, per-app allowlists, Lume VM sandbox mode.
1 maintainer
Metadata
1 maintainer
Release files for usemymac 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| usemymac-0.1.0.tar.gz | 1.3 MB | With provenance | Details for usemymac-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| usemymac-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for usemymac-0.1.0-py3-none-any.whl |
Total release size: 1.3 MB
Release files / usemymac-0.1.0.tar.gz
| Download URL | usemymac-0.1.0.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e65ff7b8e0942232525a7945f0a15b66b95eeb3cdb065d8f7ad2f76e746c1876
|
|
BLAKE2b-256 checksum How to use checksums |
e0e9b8a017b207fd17235e2a80f8391ed9a89f672fddb8fb6fcad5e6403cde2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logRelease files / usemymac-0.1.0-py3-none-any.whl
| Download URL | usemymac-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0001f512c5585989195b9cc51e835aa0d574716b6914b1dcca99f4e40782c93
|
|
BLAKE2b-256 checksum How to use checksums |
0ea59862933bc23423726849451db611a786a4eb380ac5305dc0a46c4785998c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logSecurity for usemymac 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for usemymac-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
