Open an aindrive drive as a read-only folder in Memona #1
Reference in New Issue
Block a user
Delete Branch "read-only-folder"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A new provider opens an aindrive drive through the drive's own MCP endpoint, with the Server URL and an access token from its MCP panel. Folders list, files read up to aindrive's 8 MiB, and a file that changes between the stat and the read is a conflict, never a mix of two versions. Reads decode base64 in place, so any 1 MiB slice fits Memona's per-call fuel.
Verified: 27 unit tests, clippy, rustfmt and the wasm32-wasip2 build pass, and the component ran in an isolated Memona 2.0.0-alpha.49 against a live drive; downloaded files matched their SHA-256.
🤖 Generated with Claude Code
@bot please review the head of this pull request: the aindrive MCP client, the base64 path that keeps reads within Memona's per-call fuel, and the error mapping to the filesystem contract.
✅ Approved
Read-only aindrive provider is ready to merge.
Strengths
Checks
cargo fmt --checkcargo clippy --locked --all-targets -- -D warningscargo test --locked --lib— 27 passedcargo build --locked --release --target wasm32-wasip2CI / checks (pull_request)— passedDeclined to judge