Understand saved files and editor changes
Use the saved Cloud project version when reading files through MCP.
Cloud MCP reads file content stored in the Cloud project. The editor holds the changes you are working on; saving writes those changes to the project.
From editor changes to a saved-file read
Unsaved edits
Saved Cloud content
Editor
Unsaved edits → Saved file: Save and confirm
Saved file
Cloud project
Saved file → Saved-file read: Read saved content
Saved-file read
MCP client
Saved-file read → File version and manifestVersion: Identify saved content
File version and manifestVersion
MCP client
Save before reading
Save the edits you want the client to read and confirm that the save has completed. Choose the intended project and a path from its saved-file list.
Identify the saved version
The saved-file read contract includes a complete-file version and a project manifest version. Use these identifiers when checking which saved content a summary is based on.
Continue the same read
When a file is returned in chunks, follow the continuation offset and compare the file version and manifest version across chunks. Use the guide below if the file changes during a read.