Tano brings Markdown documents, workspaces, and collaboration tools into one view. First locate the source content, then decide whether to connect devices or agents.
Documents and workspaces
Document content is Markdown. A title and path help you find a file, but its path is not its permanent identity. A local desktop workspace uses a folder you choose; an online workspace stores files on a service; the browser demo uses storage in the current browser.
| Mode | Content location | Account or server required |
|---|---|---|
| Browser demo | Current browser | No |
| Local desktop workspace | .md files in the selected folder |
No |
| Online workspace | Workspace service | Sign-in required |
These modes do not merge content just because you use the same account. A local desktop workspace can be explicitly connected through file sync to an authorized remote workspace.
File identity and application data
A workspace UUID and short file IDs help identify documents after a rename or move. Portable workspace identity, objects, relations, and rules live under .tano/; content stays in ordinary Markdown files. Search indexes, unsaved drafts, sync queues, and personal settings belong in device application data.
Move or back up both ordinary files and .tano/. See File identity and Backup and recovery for the matching and recovery limits.
Sharing content with an agent
On desktop, an agent you configure can access the same local folder or use local MCP tools to read and conditionally write Markdown. When another tool changes a file, Tano compares the editing baseline, merges independent edits where possible, and preserves both sides on conflict. See Work with an agent.