Set-up guide

1 · The one rule worth knowing

Your licence opens the same full app through two doors:

Now the rule: browsers keep a separate library per address. The maps you make in the app live at tabtree.app; the maps you make in the file live with the file. Neither is lost — they are two shelves. The bridge between shelves, and between machines, is the 🛟 folder below.

2 · First run (2 minutes)

1. Open tabtree.app/me and enter the key you received.
2. Install it: in Chrome or Edge, click the install icon at the right end of the address bar (a screen with a down arrow). TabTree gets its own window and Dock icon.
3. Click ✨ Templates and start from a real map — OKRs, meeting minutes, org chart — or press Tab on the canvas and just type.

3 · Your maps on every machine — the 🛟 folder

TabTree has no server, so it syncs the way you already sync files: it writes every map, as it changes, into one folder you choose — one .tabtree file per map. Put that folder inside iCloud Drive, OneDrive, Dropbox, Google Drive or Syncthing, and they carry it between machines. TabTree on the other side picks it up.

On your first machine

1. Open 🗂 Maps (the library), click 🛟.
2. Pick — or create — a folder inside your synced drive, e.g. iCloud Drive/TabTree or OneDrive/TabTree.
3. Done. Every map is written there now, and rewritten on every change.

On your second machine (or the file, or another browser)

1. Wait for your drive to finish syncing the folder (icon in the menu bar).
2. Open TabTree there, 🛟, point it at the same folder.
3. Your library arrives on its own: 🛟 N map(s) imported from this folder

Day to day

• Nothing to do. TabTree catches up when it starts and when you come back to its window: 🛟 1 map(s) updated from the folder
• Edited the same map on two machines before they could sync? Nothing is ever overwritten: you get both versions side by side, the second named “… (folder copy)”. Keep the one you want, or merge by hand.
• Deleted a map? The deletion travels to your other machines too — and the map's file is kept in the folder's Corbeille/ (trash), so nothing is ever gone for good. An edit always beats a deletion: if you changed a map here while deleting it elsewhere, the edited version survives.

4 · “My library is empty!” — it isn't

Sooner or later you'll open TabTree somewhere new — another browser profile, another machine, the downloaded file — and see an empty library. Nothing is lost. You're looking at a different shelf (rule #1). Two ways back:

• Click 🛟 and point it at your folder — the whole library is adopted automatically.
• Or use the “I already have maps” card shown on any empty library.

5 · The fine print, in plain words

• Your key activates up to 5 browsers — 20 on Studio. The activation screen lists them and lets you release one, so a machine you no longer use stops costing you a seat.
• Activation happens once per browser, and then never again. After it, the file never talks to any server: open it on a disconnected laptop and it works, forever.
• Your maps never reach us. They live in your browser and in your folder. Apart from that one activation, the only network calls the app ever makes are the AI features — directly to your AI provider, with your key, only when you use them.
• Updates: the hosted app is always current. The file updates when you download a fresh one from tabtree.app/download — your maps stay where they are either way.

6 · If something looks wrong

• “Reconnect folder” after restarting the browser — normal in a plain tab: Chrome forgets folder permissions between sessions. One click. Install the app (§2) and choose “Allow on every visit” to retire it.
• A map came back after I deleted it — it was edited on another machine after you deleted it here. Edits win over deletions, by design.
• Two copies of a map — that's a conflict kept safe (“folder copy”). Delete the one you don't want; the deletion will travel.
• Anything else — write to us, and say which door you were using (file or app) and what the 🛟 button says. That's usually the whole diagnosis.