Local workspaces, online workspaces, and the browser demo use different storage locations. Check where content is saved when choosing a workspace.
Local workspaces
Markdown documents and attachments remain ordinary files in the folder you select. A local workspace does not require an online account. Other editors, Git, and tools with file access can work on the same files.
Portable Tano data lives under .tano/, including workspace identity, objects, relations, rules, templates, and document suggestions. Caches, interface preferences, and local activity records live in device application data. Markdown remains the content source of truth.
Assistant sessions and reference snapshots, calendar connection settings, and sync state stay in device application data. Keys and tokens stay in the system credential store. Copying a workspace does not copy connections or chat history. Accepted assistant edits become Markdown; proposals published as document suggestions live in .tano/suggestions/ until reviewed.
Include documents, attachments, and .tano/ in a workspace backup. Backing up content alone does not preserve all workspace identity and relationship data.
Online workspaces
Online content is stored by the workspace service. The browser keeps necessary session and interface state. Workspace permissions determine each member's editing capabilities; documents are read-only for members with only reading access.
Signing in to the same account does not automatically upload a desktop folder. These are separate modes, but desktop can explicitly connect file sync. See Online workspace.
Browser demo
Demo documents stay in the current browser and are not connected to an online account or desktop folder. Clearing browser data can remove demo content. Export or back up important documents separately.
Continue with Browser demo and Local desktop workspace.
Data tables and agent records
Data-table fields, records, formulas, and shared views live in ordinary .table.json content files. Markdown table text stays in .md; additional document widths and colors live under .tano/. Device spreadsheet drafts and original-file backups stay in application data.
Local agent connections, queues, and sessions are device application data; portable agent person identities live under .tano/objects/. Hosted task queues and execution sessions are stored by the connected service and have a different boundary from local assistant history. See data tables and agent workflows.