mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-17 03:12:19 +03:00
f01a8a9e7c
- Transfer streams: each 8 MiB base64 chunk read off the source is posted to the cloud agent's /api/ops/transfer/chunk as it is (retry with backoff, offset_gap re-sync), then /transfer/restore. Peak memory is one chunk; no multipart, so a first native Cloud sign-in (cookie session only) uploads over the same JSON path every other call uses. - A cloud agent without `import_keep_host` in /api/status gets "This cloud agent needs a Hermes update before it can receive a transfer." before anything is read or uploaded (BearHuddleston's finding and test idea). - The undo point reaches the UI from the import's status as soon as it exists, also on failure; the error screen offers Undo next to Retry, and Undo always restores the FIRST undo point of that agent (a retry never replaces it). An import that finished without one is an error. - Cancel is offered while backing up and copying only; once the restore is requested it is gone (it cannot be stopped). - One backup implementation: hermes-cloud-agents `backup()` reuses runBackup; the save downloads /api/ops/backup/download from the backend that wrote the archive (never /api/fs/download, which an SSH backend serves remotely). - Webapp: sign-in reuses the connection the saved-connection OAuth created (no duplicate save); "Sign in" sends a signed-out Webapp to Settings > Providers; the remote-browser paste field is mounted in the transfer card. Co-authored-by: BearHuddleston <196404565+BearHuddleston@users.noreply.github.com>
f01a8a9e7c
·
2026-11-16 10:29:52 -08:00
History