hermes-yandex-disk

Your Yandex Disk, handed to the agent. It can walk the folders, read a file into the conversation, write the answer back, and give you a share link — without you opening a browser.

"Read me the March invoice in /Documents/Accounting." "Save these meeting notes to /Notes/2026/ and give me a link." "What's eating my Disk space? Move the old videos into /Archive." "Restore that file I deleted this morning."

• 🔒 YANDEX_DISK_ROOT sandboxes the agent to one folder — every path is checked against it, including ones the model invents and ones it copies back from an earlier result.
• 🛟 Nothing is overwritten or destroyed by accident — writes, copies, moves and uploads refuse an existing destination unless you pass overwrite, deletes go to the bin by default, and the bin can be restored from. Replacing is never done by clearing the way first: an upload from a url is staged beside the target and moved over it once Yandex has finished fetching, and a download writes beside the local file and moves over it once the transfer is complete. A transfer that fails costs you the new copy, never the one you already had.
• 🎚 YANDEX_DISK_ACTIONS decides what the agent may do at all — a tool outside the allow-list is never registered, so it cannot be called or talked into being called.
• 📂 Fourteen tools over one credential — browse, read, write, upload, download, copy, move, share and restore, all through the REST API — plus a fifteenth, yadisk_search, wherever the token is allowed to use Yandex's search endpoint.
• 🔑 One OAuth token, nothing proxied — the plugin talks to cloud-api.yandex.net directly; no third-party service sees your files or your token.

Tested against Hermes 0.19.x, Python 3.11–3.13.

Quick start

# 1. Install the plugin into your Hermes environment
hermes plugins install akinfold/hermes-yandex-disk/hermes_yandex_disk --enable

# 2. Add your token — issue one at https://yandex.ru/dev/disk/poligon/
#    (scopes: cloud_api:disk.info, cloud_api:disk.read, cloud_api:disk.write)
echo 'YANDEX_DISK_OAUTH_TOKEN=y0_your_token_here' >> ~/.hermes/.env

# 3. `--enable` already wrote this into ~/.hermes/config.yaml
plugins:
  enabled: [yandex-disk]

Restart Hermes and ask it: "How much space is left on my Yandex Disk?"

Not ready to hand over write access? Add YANDEX_DISK_ACTIONS=read to ~/.hermes/.env and the agent gets a read-only Disk. See Choosing what the agent may do.

The tools

Every read result carries the path the write tools take as input, so the agent can chain them without guessing.

Changed in 0.5.0. yadisk_upload from a url used to ignore overwrite. Yandex' fetch-from-internet endpoint has no such parameter and the plugin did not stand in for it, so an upload onto a path that was already taken did whatever the server decided — the API documentation does not say what. It is now refused unless you pass overwrite=true, the same as every other write. If anything of yours uploads by URL over a file that is already there, add the flag before upgrading.

Configuration

Put them in ~/.hermes/.env — Hermes reads it in gateway and subprocess runs too — or export them in the environment.

The two byte limits take a whole number of bytes and the timeout a number of seconds, fractions allowed. A value that is not a number, or is zero or negative — 5MB, 60s, 0 — is ignored without an error and the default applies.

Two further limits are fixed and cannot be configured. A request answered with 429, 500, 502, 503 or 504, or one that fails to connect, is retried up to three times (honouring Retry-After, capped at 30 seconds), so a single call can take longer than YANDEX_DISK_TIMEOUT. Large copies, moves, deletes, restores and bin operations run as deferred operations on Yandex's side; the plugin waits up to 60 seconds for one to finish and then reports that it is still being processed. Such an operation usually completes on its own, so check with yadisk_list before retrying.

Confining the agent to one folder

YANDEX_DISK_ROOT=/Hermes

Every path the agent gives is then interpreted relative to disk:/Hermes, and anything that resolves outside it — an absolute disk:/Private/..., a ../ climb, a path pasted from somewhere else — is refused before a request is made. Results are rewritten so the agent never sees the prefix: every path it gets back is relative to that folder — disk:/Hermes/notes.md comes back as /notes.md — and can be handed straight to the next tool. The agent sees a disk whose root is that folder. The bin is filtered the same way: items deleted from outside the sandbox are neither listed nor restorable, and emptying the whole bin is refused, because the bin is shared with the rest of the account.

Choosing what the agent may do

YANDEX_DISK_ACTIONS=read,write      # no deleting, no sharing
YANDEX_DISK_ACTIONS=read            # a read-only Disk
YANDEX_DISK_ACTIONS=list,read_file  # exactly two tools

search is capability-gated: Yandex grants its search endpoint per application rather than per token scope, so the plugin probes it once at load and registers the tool only if the probe succeeds. Granting read therefore also grants a whole-disk search wherever the token is allowed to run one; name the tools individually to withhold it.

Groups and individual tool names mix freely, with or without the yadisk_ prefix, so you can paste straight from the tool table above. A name that matches nothing is dropped: a typo can only ever withhold a tool, never grant one, and a value naming nothing valid (none, say) registers nothing at all. An empty or blank value counts as unset and therefore registers every tool. Filtering happens when the plugin loads, so restart Hermes after changing it.

Getting the credential

1. Open https://yandex.ru/dev/disk/poligon/ signed in as the account you want the agent to use, and issue a debug token — the fastest route, and what it gives you is an ordinary OAuth token.
2. For a long-lived setup, register an app at https://oauth.yandex.ru/ with the scopes cloud_api:disk.info, cloud_api:disk.read and cloud_api:disk.write, then run the usual OAuth flow.

Yandex Disk is free up to 5 GB and the API costs nothing to use. The token is the only credential needed — see Why REST and not WebDAV for why there is no app password to store.

Installing

A. From Git (recommended)

hermes plugins install akinfold/hermes-yandex-disk/hermes_yandex_disk --enable

Note the /hermes_yandex_disk at the end. The plugin lives in that directory, not at the repository root, and Hermes reads the manifest from whatever you point it at. Name the directory and the install is a plugin: Hermes prompts for YANDEX_DISK_OAUTH_TOKEN, installs under the manifest name yandex-disk, and --enable enables that name. It also scans only that directory, so the tests and workflows in this repository stay out of the security report.

Point it at the repository root instead and the install still appears to succeed, but it copies a directory with no manifest and no register(ctx) in it: Hermes warns that it "may not be a valid Hermes plugin", asks for nothing, and enables the repository name, which nothing answers to. hermes plugins list then still shows yandex-disk — the package nested in the clone is found — but shows it as not enabled, which is the symptom to look for. If you installed that way, remove ~/.hermes/plugins/hermes-yandex-disk and install again with the directory named.

B. From PyPI — discovered through the hermes_agent.plugins entry point:

pip install hermes-yandex-disk

Then add yandex-disk to plugins.enabled in ~/.hermes/config.yaml.

C. Drop-in — unzip hermes-yandex-disk-plugin-<version>.zip from a release under ~/.hermes/plugins/ so you get ~/.hermes/plugins/yandex-disk/plugin.yaml, then enable it the same way.

Why REST and not WebDAV

Yandex Disk exposes both a REST API and a WebDAV endpoint. This plugin is REST-only, because WebDAV covers strictly less: no bin, no public links, and no reporting for the deferred operations that large folder copies and deletes turn into. rclone's Yandex backend made the same call. The one thing WebDAV adds — an app-password login — is not worth a second stored credential for capabilities the REST API already has.

Development

python -m venv .venv && . .venv/bin/activate
pip install -e '.[dev]'

pytest --cov=hermes_yandex_disk --cov-report=term-missing   # unit tests, no network
ruff check . && ruff format --check .
radon cc -s -n C hermes_yandex_disk                         # must print nothing

Running the live E2E tests

These create, publish and permanently delete real files. Use a throwaway Yandex account. Each test works inside its own hermes-e2e-<id> folder, permanently deleted in teardown even when the test fails. Two things reach outside it: the bin tests pass their files through the account-wide bin and remove their own entries, and — only when the token is allowed to search — one test creates a single marker file in the disk root and permanently deletes it again.

Locally, put the token in ~/.yandex-disk-oauth (and optionally the login in ~/.yandex-disk-login) and run:

pytest -m e2e -v

The suite skips itself when no credentials are available, and an environment variable wins over the file: YANDEX_DISK_OAUTH_TOKEN for the token and, optionally, YANDEX_DISK_E2E_LOGIN for the account login the tests check yadisk_disk_info against. On GitHub Actions, run the E2E (live) workflow manually; it reads the secrets YANDEX_DISK_OAUTH_TOKEN and, optionally, YANDEX_DISK_E2E_LOGIN from the yandex-disk-e2e environment, and its install_hermes input (on by default) also installs hermes-agent, so the real credential resolver is exercised.

Related Hermes plugins

Part of a family of Yandex plugins for Hermes Agent:

• hermes-yandex-mail — search, read, flag, move, and delete Yandex Mail messages over IMAP, and send over SMTP when sending is switched on.
• hermes-yandex-calendar — list, create, update, respond to, move, and delete Yandex Calendar events (CalDAV).
• hermes-yandex-search-api — Yandex web search backend and generative, cited answers for Hermes (Yandex Search API).

Contributing

See CONTRIBUTING.md. Please report security issues privately rather than as a public issue.

License

MIT — see LICENSE.