Open the owning workspace

Open the intended workspace in the matching Mac app. Its bundled helper exposes Roboty.app/Contents/MacOS/RobotyAgent cli and RobotyAgent mcp. Use your actual app path and the same private workspace root throughout. Omitting --port discovers and checks that running owner. A stopped workspace must be opened through its normal owner. The helper never starts another copy.

For example, a local owner can discover supported actions with:

/Applications/Roboty.app/Contents/MacOS/RobotyAgent cli discover --owner

Use --root /absolute/private/workspace when the running workspace uses a custom location. Local owner access and a delegated agent credential are separate routes. Review enrollment and delegation below before connecting an external client. An agent's own operating-system access is outside the tool's restricted credential boundary.

The host can serve application actions with its display off or screen locked while it remains awake, logged in and able to read its protected storage. Sleep, logout and secure-storage prompts can still require the person. This does not change the Mac's power or lock settings. UI clicks and screenshots have their own desktop requirements. See Mac availability.