Transfer files with scoped authorization

Connector 0.1.4 supports private object storage for file.transfer. Your administrator must enable the backend and both participating Connectors must be updated. ADC handles authorization, approval and task state; file bytes travel directly through storage.

adc transfer upload sends a local Agent file to an authorized device without registering a source Node. The destination verifies the file and commits it without overwriting an existing path. Keep the same arguments and idempotency key when resuming after approval.

adc update
adc transfer upload --help

Follow the existing task

An upload response contains the existing jobId. Use task.wait to follow the destination result. Upload completion alone does not mean the destination has committed the file.

adc invoke task.wait --args '{"jobId":"job_example","waitMs":4000}' --json

Check destination access

Grant file.transfer and access to the destination folder. Device-to-device copies also require source access. Owner approval applies before transfer starts, and cancellation stops pending storage requests.