The host reads a file one 1 MiB slice per call, and every slice fetched
the whole file again, so an 8 MiB file crossed the network eight times.
The last file read is now kept for the slices that follow: each slice
still stats the file first and reuses the reply only at the same
revision, so a file changed in between is fetched afresh.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A token that may write opens a writable folder. A save sends the file
whole through write_file with the revision it was read at, or "none" for
create-only, so aindrive refuses it as a conflict when the file moved on;
saves are capped at one 1 MiB transfer, which a table-driven encoder fits
into one call's fuel. A save whose answer is lost, or that the drive's
device timed out on, is reported with an unknown outcome. Deleting takes
one file; folders are refused because delete_path is recursive and
listings hide entries such as .git.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The plugin reaches a drive through aindrive's remote MCP endpoint with
the drive's access token. Opening a connection asks which tools the
token may call, so it works while the drive's machine sleeps. Listing,
stat and reading map to list_files, stat and read_file; a read is
statted first, and a file whose length changed in between is refused as
a conflict. Reads decode only the window asked for, straight from the
reply pieces, so any 1 MiB slice of a file up to aindrive's 8 MiB limit
fits Memona's per-call fuel.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
RaymondCho