Version 1.0.53
GitHub Release v1.0.53 — release record and artifacts →
Added
remote_pull(code, path)andPOST /api/v1/pullcopy one regular file from a connected machine into a temporary relay blob and return a download link.- Account-only
remote_push(code, blob_id, dest_path)andPOST /api/v1/pushwrite a stored blob onto a machine. POST /api/v1/filesuploads caller-owned bytes, andGET /api/v1/files/{blobId}downloads an authorized blob.
Changed
- Transfer calls use a roughly 55-second request deadline, returning a clear failure before the MCP client's usual 60-second timeout.
Security and limits
- Each transferred file is limited to 100 MiB. A download link expires after 1 hour, and blob access expires after 24 hours; an hourly, retrying sweep removes inaccessible expired bytes afterward.
- Caller uploads and pushes require a signed-in account. Anonymous callers may pull only during a session code's first-hour access window.
- Push writes are atomic. Directories must be archived into a regular file, and larger artifacts should use user-controlled object storage or an artifact registry.