Find files on Yandex Disk and crunch the exports

The agent calls the Disk REST API at cloud-api.yandex.net and works with the tree of the connected account: it lists folders and files, reads metadata — name, type, size, modification date — finds a document by name, extension or folder and hands over the link instead of making you scroll. It also picks up an export or report straight from Disk, runs the numbers on it and keeps an eye on remaining space and on new files appearing in your work folders.

One trait of Disk is worth knowing up front: a file can only be put there from an external URL — the API does not allow passing contents directly. So the agent returns the result of a calculation through a link rather than as a stream of bytes. Someone else folder enters its field of view only after the owner grants it View or Edit in the sharing settings, and whatever is deleted goes to the trash, where it can still be retrieved.

On the write side the agent creates folders, copies and moves files, deletes what is no longer needed and publishes links to documents you have to share. It asks before overwriting a file with the same name and before deleting, and it treats publishing as a decision of its own: a public link opens the document to anyone who receives it, and in work folders that call is yours, not the agent's. What it put where is stated explicitly, as a path rather than a «done».

Large operations — copying or moving a folder — are performed asynchronously by the API: the response is a link to a status, and the agent waits for completion instead of reporting «done» halfway. The Disk REST API cannot open access to a single folder, rights always cover the whole Disk, which is why limited access is set up as a separate account. The agent holds the request rate itself, and it calls an empty folder empty instead of staying silent.