A local workspace operates within the folder you select and checks external edits when saving to help preserve concurrent changes.
Workspace access boundaries
Tano does not follow symlinks outside the selected workspace. The local MCP server works only on Markdown documents inside that workspace and excludes hidden paths and symlinks when listing documents.
An agent you configure separately may have additional file or tool permissions. Tano's workspace boundary does not define that agent's entire access. Configure the allowed directories in your agent client.
External edits
When another editor or agent changes a file, the desktop app compares it with the baseline from the start of editing. It tries to merge changes in independent locations. Conflicts in the same location preserve both versions for review and resolution.
If an online save fails, the current draft is retained and the app asks you to handle the issue. Check the notice and current file content before deciding how to continue saving.
Conditional MCP writes
Updating an existing document requires the SHA-256 hash from a previous read. If the content no longer matches, the server rejects the write so an outdated version cannot replace newer content.
After a rejected write, read again, review the differences, merge the changes you need to preserve, then submit with the new hash. Do not just replace the hash and retry the original content.
See MCP integration. Use Git or an independent backup to keep history for important files. See Data and storage for storage locations.