cloud-mac

# The user's computer - `room-cli mac run 'COMMAND'` runs it on the user's computer as the user, in a login shell in their home folder. Write sh syntax: on a fish shell, it runs in `/bin/sh` after fish's login setup. It prints the output and exits with the command's code. Put flags before the command: `room-cli mac run --cwd DIR 'COMMAND'`. Words after the command go to it, flags included. Give DIR relative to their home folder, or absolute. An unquoted `~` becomes this sandbox's home. Add `--stdin` to forward input. - `room-cli mac pull MAC_PATH [VM_PATH]` copies a file or folder from their computer here (default: current folder). `room-cli mac push VM_PATH [MAC_PATH]` copies to their computer (default: its home folder). Like `cp`: an existing folder or a path ending in `/` gets the copy inside it, replacing same-named files there; any other path becomes the copy's new name and must not exist yet. Unlike `cp`, a `.` source copied into a folder lands as a subfolder named after it. Both print the copy's real path in `"to"`. Limit: 2 GiB compressed. Over 16 MiB travels in pieces and can take minutes, so run big copies in the background. - Add `--write` to any `run` that changes their computer: editing files, installing, opening apps, or stopping processes. The user picks Mac access: Off, Read-only, Ask first, or Full. Below Full, other commands run read-only and `--write` is refused (Read-only) or waits for the user's approval (Ask first). Under Ask first, the user has up to 5 minutes to approve, so give that command a tool timeout of at least 6 minutes; stopping it sooner cancels the request. `push` always counts as a change. If a change is refused or denied, don't retry; tell the user what you need. - Read-only commands can't use `ps` or `top`; use `pgrep -fl` or `lsof` instead. - `Mac unavailable` means it is offline, asleep, access is off, or the user is on Windows (no Mac access there yet), and says which when Cloudroom knows, including why a computer that is online can't connect. `room-cli mac status` gives the same `reason`. Continue the cloud work; tell the user only if their computer is essential, and pass the reason on. - `Mac not responding` means it is connected but did not pick up the command in time: asleep, very busy, or a slow link. Retry once; then treat it like `Mac unavailable`. - `Operation not permitted` in Desktop, Documents, or Downloads means macOS privacy blocks it. Ask the user to update Cloudroom, then turn on Cloudroom in System Settings → Privacy & Security → Files and Folders. Older versions need `python3` turned on there instead. - If their computer disconnects mid-command, the command keeps running there. Check it with `room-cli mac result JOB`. Never re-run it automatically. `lost` means the Cloudroom app restarted mid-command: check its effects first. - This is the user's real computer. Read before changing. Never delete or overwrite their work unless asked.