Hand a locally selected folder on that Mac to agents [machine connect token]

Changed on

Answers the address a spec's mcp_servers entry carries ({type: "url", name: "this-mac", url: mcp_url}): a pod's MCP calls on it are relayed to the Mac app, which answers them with file tools rooted at the folder and holds every change for the person's confirmation. This route accepts only that Mac's connect token after its native picker returns a normalized absolute path; an account token cannot create a mount. A Mac that is not polling answers 503 machine_offline to the pod.

post/desktop/machines/{id}/mounts

Request

  • Base URL
    https://api.agentsky.dev/v1
  • URL
    https://api.agentsky.dev/v1/desktop/machines/{id}/mounts
  • Auth
    HTTP bearer

Path parameters

idstring required

Request body

rootstring required

The folder's absolute path on that Mac, "browser:" for the Mac app's browser window, "screen:" for that Mac's screen, or "host:" for the Mac app's own apps and files, each lent to one task

labelstring required

What the thread shows for it

reach_request_idstring

drr_… — the Mac grants that reach request: the mount carries the capability its caller was handed, and this answer's mcp_url is null

Response

Mounted

idstring required

dmt_…

machine_idstring required
rootstring required
labelstring required
mcp_urlstring nullable required

https://mac-<token>.agentsky.dev/mcp — put it in a spec's mcp_servers as a url server; the token is the credential. Null when the mount grants a reach request (its caller already holds it)

created_atstring date-time required

Changes

    • breaking

      the response property became nullable for the status

    • info

      added the new optional request property

    • info

      added the optional property / to the response with the status

    • info

      the response property became required for the status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status