Mind Map (build a map with the keyboard or the mouse)
A mind map you build inside Omniscio: open it, add nodes with the keyboard or by dragging, edit their text and attach hidden notes, drill into a layer behind a node, or narrow the canvas to one branch to work on it alone, turn an idea into a task, a board item or a link to a Vault note, and change how the whole map looks. Covers the saved-maps library and where a map goes when you are done with it.
On this page
What it is
Status: available to everyone, on by default. Mind Map is on for every install with nothing to flip, and its Settings → Features → "Mind Map" switch turns it off if you do not want it (the setting is
mindmapEnabled). An install that saved the old off default is switched on once at upgrade.
What it is — A standalone mind-mapping canvas built into
A standalone mind-mapping canvas built into Omniscio — separate from the coding sessions. You build a single-rooted tree of text ideas, the app auto-arranges it, and you can save a whole library of maps, theme them, import and export them, get AI help filling them out, and publish a read-only share link.
The drawing surface is a pan/zoom canvas (powered by React Flow); the layout arranges itself automatically (powered by d3) so you never drag boxes around just to keep things tidy — you focus on the ideas and the map lays itself out in one of four directions (left→right by default, plus right→left, top→bottom, bottom→top).
An AI agent can drive it too. Everything on this page is also available on Omniscio's
control server under the /mindmaps routes — listing, reading, creating, editing, linking and
sharing maps — so an agent can build or tidy a map for you; see part 2 for
the details.
Where to find it
The Mind Map panel in the sidebar — its own feature, turned on by default (switch it off in Settings → Features to hide it everywhere). Opening it shows your current map (or a fresh blank one), with your saved-maps list beside it.
Opening it & the saved-maps library
- Open it from the toolbar (a network-of-nodes icon) — or from anywhere with Ctrl+M (on a Mac, Option+Shift+Command+M; rebindable in Settings → Keyboard Shortcuts; it does nothing while Mind Map is switched off in Settings → Features). Either way it opens docked inside the app by default: project bars on the far left, your saved-maps list in the session-sidebar slot, and the editor (header + toolbar + canvas) filling the main panel. A maximize button in the header flips to a full-screen view and back; your choice is remembered. Opening always lands you on your current map. With none open it lands on your most recently updated saved map once the saved-maps list has loaded, and on a fresh blank one only when you have no saved maps (a blank map you have already typed into, or one you asked for with New map, is never swapped out).
- The Mind Map has its own hub. It is a normal sidebar hub (like Calendar), so the sidebar and the header trail always name the map you are looking at. Opening the map from the toolbar or Ctrl+M selects that hub, clicking the hub row opens or resumes the map, switching to any other hub closes the map, and the editor's close button returns you to the hub you came from. Alt+Q therefore works from inside a map — even with the cursor in a node's text box: one press takes you back where you were, the next brings you and the map back. The Mind Map hub is never the hub a fresh launch opens on.
- Pop the map out. The pop out button in the editor header moves the map into its own window — saved-maps list beside the canvas — so it can live on a second monitor while the rest of the app stays put. The window remembers where it was and reopens on the same map next launch. The same thing is on the Mind Map hub row's Open in new window. A popped-out map shows changes saved from anywhere else — an AI session editing it, another window — the same way the docked map does. Its sidebar has no Sessions tab, because that window has no place to show a session chat: pick or start a Mind Map session from the docked map in the main window. Two windows on one map warn rather than sync: the map that saved last wins, and the app tells you it reloaded or deferred your edit.
- New to it? Take the guided tour. Start it from the Take a tour button in the Mind Map toolbar (next to the "?") or from the Mind Map row in the toolbar's Tours menu. It is never offered automatically — no toast and no inbox card — and the button only appears in the desktop app's main window (not a popped-out map), while the feature is on.
- Prefer to watch? A short Mind Map tutorial video is in Tutorial videos.
- Your maps belong to the account you are signed in with. The saved-maps list shows the maps made under the account you are signed in with. A map made before accounts existed carries no owner at all, so every signed-in account on this computer still sees it in its list; opening it does not take it away from anyone, and any of those accounts can open, change, share or delete it. Nothing in the list marks those older maps yet, so if more than one account uses this computer, treat a map older than your account as shared. While your Omniscio workspace requires sign-in, Mind Map asks you to sign in before it opens, and every map call is refused until you do.
- Switching accounts does not bring your maps along. Maps made while you were signed in with one account never show under another, and the app has no way to move them. To carry a map over, sign in with the old account, use Export → JSON on each map, then sign in with the new account and Import each file. Each import is a brand-new map: it counts toward the new account's map limit, its ideas lose their task and board-item ties, and share links, project attachments and AI sessions stay with the old map. Do this while you can still sign in with the old account: erasing an account's data deletes its maps too.
- Every map auto-saves a moment after you stop editing (to a local database) — there's no Save button. A brand-new map is saved, and joins the saved-maps list, the moment it holds something: the first idea you type, a note, or anything inside a layer. A new map you open and leave blank is not kept.
- A save that fails says so and offers the next step. The header reads "Your mind map didn't save." beside a Try again button that saves the map again (for a brand-new map, it retries creating it). When the save was refused because the map changed somewhere else while you were editing, the header says that instead and offers no retry: finish your edit and the newer version loads. A change that fails to save after you have switched to another map gets its own message naming that map, with Try again unless the map is gone or the change can never save; the change is also kept and sent again when you open that map, so the app's general "kept and will be tried again" notice is not shown on top of it. A list of maps that will not load offers Retry, a newer version that will not load says an older copy is on screen and offers Reload, and clicking another map while a new map cannot be saved explains why the new map stayed open.
- Works offline. Maps are built and saved on this computer, so you can create and edit them with no internet connection. The two AI features (expanding an idea and generating a map) and Share need a connection; without one they show an error and your map is unchanged.
- Using two computers. Mind maps travel with a Portable Backup import, with Backup Mirror's Sync now and with its Restore from file in Merge mode, and they merge differently from everything else: for each map, the copy that was changed most recently wins. If the other computer edited a map after you last changed it here, its version replaces yours, and a map that was deleted there after your last edit here is deleted here too. Your replaced version is kept as a hidden deleted map, named after the map with "(replaced by sync" and the date and time added, but nothing in the app can open it yet (see If a map goes missing). Before merging, export any map you want to keep as it is (Export → JSON).
- Manage a saved map from its row. The rows carry no always-visible buttons — right-click a map (or press-and-hold on touch) opens a small menu with Rename, Duplicate and Delete. Duplicate makes a copy — notes, web, idea and Vault links, styles, sub-maps and view settings — titled "<name> (copy)" and opens it. The copy keeps the original's title lock: a copy of a map whose title you typed keeps its title when you edit its root. Ideas in the copy are not tied to tasks or board items; those ties stay with the original. A duplicate counts toward your plan's map limit like any new map. Delete still asks you to confirm ("Delete mind map?"); there's no separate undo, so the confirmation is the safety net. (Renaming from the menu is the same inline edit as double-clicking the title.)
- Search your maps. A search box under the Maps tab (shown whenever you have at least one map) filters the list by title as you type; an ✕ clears it, and a query that matches nothing shows "No maps match your search." with a Clear search button.
- An empty list says why. With no saved maps the list offers a New map button; while the map on the canvas is a brand-new blank one, the list instead says it will appear there once you add an idea.
- A new map opens with the cursor already in the root ("main") node — a blank, focused field — so you can type the title the instant it appears, no click first. While that first box is blank it shows gray example text: "Type an idea, then press Tab to add another".
- A new map is titled "Untitled" until you type into the root node — then
the title auto-derives from the first 40 characters of that text plus the map's
created date (e.g.
Project plan — Jun 6, 2026). Renaming the map yourself — single-click the title in the editor header to edit it inline (Enter or click-away saves, Esc cancels), or double-click it in the saved-maps list — locks the title so editing the root no longer changes it.
How it behaves
Building a map with the keyboard
The canvas is keyboard-first. With a node selected:
| Key | Does |
|---|---|
Tab (or Ctrl+Enter) |
Add a child of the selected node |
Shift+Tab (or Ctrl+Shift+Enter) |
Add a parent behind the node — it slides in between this node and its parent (on a left→right map's center node it makes a left branch instead — see the note below) |
Enter |
Add a node at the current level (a sibling below; the root adds a child instead) |
Enter while editing |
Commit the text and open a fresh sibling below — so you can type a list quickly (an empty Enter ends the run) |
Tab while editing |
Commit the text and open a fresh child one level deeper (an empty Tab ends the run; the parent expands) |
Shift+Tab while editing |
Commit the text and open a fresh parent behind it to name (an empty Shift+Tab ends the run) |
Shift+Enter |
Add a sibling above the current node |
Space / F2 / double-click |
Edit the selected node |
Delete / Backspace |
Delete the node (and its branch) |
| Arrow keys | Move the selection (parent / child / sibling — mapped to the map's flow direction, see note) |
/ |
Collapse / expand the node's children |
V |
Fit the whole map into view (the keyboard twin of the toolbar's Fit button); a map too big to read whole stops at the readable size and keeps its root on screen |
Ctrl+= / Ctrl+- |
Zoom in / out on the map — only while the canvas has your keyboard; everywhere else these are the app's own text-size keys |
Ctrl+0 |
Reset the map's zoom to 100% while the canvas has your keyboard; everywhere else it still jumps to that project |
Ctrl+↑ / Ctrl+↓ |
Move the node up / down (reorder among siblings) |
Ctrl+← / Ctrl+→ |
Move the node out a level (←, outdent) or in under the previous idea (→, indent) |
Ctrl+Z / Ctrl+Y |
Undo / redo |
Ctrl+X / Ctrl+C / Ctrl+V |
Cut / copy / paste a node (and its branch) |
Ctrl+N |
Start a brand-new map (the current one autosaves and stays in the saved-maps list) |
l |
Open the selected node's layer (creates a blank one first if it has none — see Layers in part 2) |
] / [ |
Swap between the base map and the node's layer (a toggle) |
n |
Add or edit a hidden note on the selected node (see Hidden notes in part 2) |
Ctrl+L |
Add or edit a link on the selected node (see Links on a node in part 2) |
Ctrl+F |
Find an idea by its text or its hidden note (see Finding an idea below) |
| Any other letter / number / symbol | Type on the selected node: it opens for editing, starting with the character you pressed, so you can select an idea and type its words |
Esc |
Deselect (or cancel an in-progress edit); with nothing selected, press it again to leave the map and get your keyboard back — focus lands on the map's toolbar: ← / → (and Home / End) walk its buttons, and Tab moves on past the toolbar |
? |
Show the keyboard shortcuts cheat-sheet (the building, moving, layer, clipboard and view keys, grouped by category) |
The table above shows the default left→right map. Everything the keyboard does — the arrows, the Move chords, and
Tab/Enter— rotates with the map's flow direction so a key matches what you see. On a top-down map,↓walks into a child, andTabadds a sibling whileEnterdives into a child (the same while you're typing). On a four-sided spider map, each branch is driven by the way it grows, and from the center an arrow jumps to the branch on that side.
From the center ("main") node, the four create keys fan out in four directions. On a left→right map with the center node active,
Tab/Shift+Tab/Enter/Shift+Entershoot a new branch to the right / left / down / up — building the four-sided spider with no dragging. Each press from the center adds another branch on that side (so to grow a second arm you come back to the center and press again), and it works the same whether the center node is selected or you're still typing its label (the key saves the label first).Tab→ right is just the ordinary "add child"; the other three are the new directions. This is a left→right-map, center-node-only behavior — branch nodes and the other flow directions keep the meanings in the table above.
Every Move shortcut also works with Alt+Shift held instead of Ctrl (e.g.
Alt+Shift+← outdents the node) — a handy alternate when your OS already uses Ctrl+Arrow.
Don't remember the shortcuts? Press ? on the canvas — or click the ?
(Keyboard shortcuts) button on the Mind Map toolbar — to pop open a tidy
cheat-sheet of the building and moving keys above, the same way ? opens the shortcuts list
elsewhere in the app. The link, style, focus, outline, task and board-item chords
(Ctrl+L, Alt+Shift+S/B/O/D/M) and Find (Ctrl+F) are not on it; they are listed,
and rebindable, under Settings → Keyboard Shortcuts. (Desktop only; on a phone or tablet
there's no physical keyboard, so the on-screen buttons take over instead — see On a
phone in part 2.)
A collapsed node carries a small count circle on the side its children
branch from — the number inside is how many ideas one click brings into view (a
folded idea inside the branch counts as one and keeps its own circle), so you
can see there's more (and roughly how much) without expanding. The circle is a
button: click or tap it to open the branch — its hidden ideas appear, the branch
is selected, and one Undo folds it back. Hovering it explains this in plain words
("Click to show 6 hidden ideas, or select the branch and press /"), screen readers
hear "Show 6 hidden ideas", and on a phone its tap area is a little larger than the
circle. It appears only when something's actually hidden; open the node (the
circle, /, or the toolbar) and it's gone.
Connection dots appear only where a line actually connects. A node shows a small filled dot on each side a line meets it — incoming from its parent, and outgoing to its children. A dead-end (leaf) node has nothing leaving it, so it shows no outgoing dot at all (the canvas never draws an empty circle on a leaf); give it a child and the outgoing dot appears.
An "Expand all" toolbar button (an unfold icon) appears on the canvas toolbar
only while at least one branch is collapsed — one click reveals every collapsed
branch at once (a single Undo step), and the button disappears again once
everything's open. It's the discoverable, do-it-all-at-once companion to folding one
node with / — handy when a big map has several folded branches and you want the
whole picture back without hunting them down.
Adding an idea has two toolbar buttons on a computer (right after New, at
the start of the canvas toolbar), so you never need to know a key to grow the map.
Add idea puts a new idea under the selected one (under the central idea when
nothing is selected) and opens it for typing. Add idea at this level puts the
new idea beside the selected one instead; it grays out while the central idea is
selected, because the central idea has nothing beside it. Each tooltip names the
key that does the same thing for the map's current direction: on a left-to-right
map Add idea is Tab and Add idea at this level is Enter, and on a top-to-bottom
map the two swap. A phone keeps its own Add child / Add sibling buttons in
the action bar at the bottom, so these two are not shown there.
Undo and redo are also toolbar buttons (near the top-left of the canvas
toolbar) — the discoverable version of Ctrl+Z / Ctrl+Y, so you don't have to
know the shortcut. They grey out when there's nothing to undo or redo, drive the
exact same history the keyboard does, and clicking one hands keyboard focus back to
the map so the next Ctrl+Z still works. Undo remembers your last 128 changes,
enough to take back 100 ideas typed in a row; past that, the oldest change drops
off first.
Building a map with the mouse (drag)
Drag a node and what the drop means depends on where you release it, and every drop is hold-to-commit so nothing happens by accident — a candidate shows a faint green hint while you drag, and only after you hold ~0.25s on the same target does it lock in (full highlight = release now and it happens). Brush past and it clears.
You can move any node onto any other node, anywhere in the map:
- Onto another node's body → nest it as that node's child (snaps to the nearest valid node; never onto its own descendant). This includes dropping onto the central "main" node to make a new top-level branch — works in every layout direction.
- At any node's top/bottom edge → slot it in right there, just above or below that node, in that node's list (a thin line shows where it lands). This works across branches too: pull a node out of one branch and drop it between two children of another, and it auto-nests into that list at the spot you choose.
- Into the empty space on any side of the root — above, below, left, or right (left→right view only) → make it a top-level branch on that side. Pull branches to different sides and the root re-centers into a spider, arms radiating in all four directions (a diagonal drag lands on whichever side you pull it furthest toward). Each branch remembers its side.
Editing text & the node menu
- Editing opens an inline field. A node still showing its "Untitled" placeholder
opens blank; a node with real text opens pre-filled and selected. Commit with
Enteror by clicking away;Esccancels. - Typing starts the edit. Select an idea and just type: the field opens with the
character you pressed and the idea's old words are replaced by what you type —
Escputs the old words back. The map's own one-key shortcuts (/,V,l,n,[,],?) still run their command first, so a word beginning with one of those letters needs aSpaceorF2first; every other letter types straight in. - There is always one MAIN node, and you can select more. A plain click selects a single node. Ctrl-click (Cmd-click on a Mac) adds another node to the selection, or takes it back out, and Shift-click selects the whole run of siblings between the node you clicked last and the one you just clicked. Every selected node wears the ring at once, while the last node you clicked stays the main one — that is the node the note, link and colour menus act on. Delete, Cut and Copy act on everything selected, in one undo step.
- Moving on goes back to one node. Editing a node, steering with the arrow keys, clicking a row in the outline, or right-clicking outside the selection all collapse the selection back to a single node; a node you opened but never named still auto-removes itself, so an empty box can't linger.
- Abandoning a brand-new node returns you to where you were. If you add a node
(
Enter/Tab/Shift+Enter) and then bail without typing — a blankEnter/Tab, orEsc— the empty node disappears and the highlight goes back to the node you were on before you created it (not its parent). Emptying an existing node still drops the highlight to its parent as before. (A node inserted withShift+Tabis the exception — it already has a child, so an un-named one stays put as "Untitled" rather than vanishing; you placed it deliberately.) - Right-click a node for a menu with Cut / Copy / Paste (each showing its shortcut) — the discoverable version of the keyboard clipboard. It greys out what doesn't apply (Cut/Copy on the root, Paste with nothing copied). The menu also has Add note… / Edit note… (see Hidden notes in part 2), available on any node. Thin dividers group the rows (clipboard, note and link, workspace, look and focus, Delete), Delete shows in red, and a row that opens a further box ends in "…".
- Node labels support inline markdown —
**bold**,*italic*,~~strike~~, and`code`render in the node (editing shows the raw text). A[text](url)link in a label shows as plain text; the node's link badge is what opens a link. - Long labels wrap. A label grows to a max width (~240px) and then wraps onto multiple lines, growing the node's height to fit — up to 4 lines, after which it ends with an ellipsis (so a runaway label can't make one giant node). A label that was actually cut this way is never lost: hovering the node shows the whole text in a tooltip, and a screen reader reads the whole idea rather than the ellipsis. A label that fits carries no tooltip. Every node's box hugs its text — there's no empty space to the right: a wrapped node hugs its longest line (it doesn't stay stuck at the full ~240px), and a one-line node hugs its single line too (it sizes to its content, not the max width). The auto-layout keeps the same visible gap between stacked nodes no matter how tall each one is, so a wrapped node never crowds or overlaps its neighbour, and a one-line node keeps the original gap. The editor wraps as you type — the field grows wider with short text and, once it reaches the node's max width, wraps onto new lines and grows taller, matching the finished node (you're still editing one string; pasted line breaks become spaces). The exported PNG wraps to match the canvas, and so does the share page: a long label wraps to at most four lines and anything longer ends in an ellipsis, so keep long detail in the idea's note (notes open in full on the share page).
- Lines get evened out automatically. When a label wraps, the lines are balanced instead of cramming line 1 full and leaving a bare scrap on line 2: a word drops to the short line and the box gets more compact (on the canvas and the shared map). It leans fairly even by default, and evening the lines never adds a line, so nothing shifts or overlaps.
- An idea holds up to 1,000 characters. Text past that is cut off without a message, both while you type or paste and when the map saves, so put a long passage in the idea's hidden note (up to 4,000 characters) instead. A link on an idea can be up to 2,048 characters; a longer address is refused with a message.
Colouring a branch, changing its shapes, marking a node
Colour is how a reader scans a big map, and a shape tells one kind of idea from another without spending a word. Both belong to the branch, not to the one box you clicked.
- Open the style menu three ways: the Colour, shape & icon row in a node's right-click menu, the palette button on the toolbar (it styles the selected node), or Alt+Shift+S while the map has the keyboard.
- Colour picks from ten named colours — red, orange, amber, green, teal, blue, indigo, violet, pink, slate. The colour flows down the whole branch: colour the top of a branch once and every node under it follows, however deep. A node you colour yourself keeps its own colour, and its children inherit that.
- Shape offers rounded (the default), pill, ellipse, diamond, underline (a rule under the label instead of a box) and no border. Shapes inherit exactly like colours.
- An icon marks one node — flag, star, bolt, done, alert, question, heart, target, idea, bug, rocket, team, person, bookmark, pin, time, shield or code. Icons do not inherit: marking one idea never marks its branch.
- Every row has a reset chip (the circular arrow). It clears only that node's own choice, so the node falls back to whatever its branch already gives it — reset a branch's top colour and the whole branch returns to the map default.
- Colours stay readable in light and dark. Each colour has a light and a dark pair, and the map's current light/dark mode picks the one to draw — the same map reads correctly in either, and on the published page.
- Everything travels. A style saves with the map, undoes and redoes, copies and pastes with the branch, exports with the JSON, appears in the exported PNG, and is drawn on the shared page. The Markdown and Mermaid outlines carry text and structure only, so a style does not survive those two.
Working in an outline beside the canvas
The same map can be read and edited as an indented list in an Outline pane beside the canvas — the bridge from thinking to writing, without leaving the map.
- Open it with the Outline button on the toolbar (a pressed-looking button with a list-tree icon), or press Alt+Shift+O while the map has the keyboard. On a phone it opens from the Outline button on the action bar and sits below the canvas instead of beside it.
- It is the map, not a copy. Every row is one node, indented by its depth. Renaming a row renames the node on the canvas, and renaming on the canvas changes the row — there is no second version and no refresh.
- The keys build the outline. Enter adds a sibling below and starts typing it, Tab makes the row a child of the row above, Shift+Tab moves it out one level, Alt+↑ / Alt+↓ reorder it among its siblings, and Delete removes it with its branch (never the root). Double-click or F2 renames a row; Escape keeps the old label.
- The arrow keys walk the tree the way a tree expects. Home and End jump to the first and last visible row, → opens a collapsed branch and then steps into its first child, ← folds an open branch and then steps out to the parent, and typing a letter jumps to the next row starting with it. Escape leaves the pane and returns the keyboard to the canvas.
- Drag a row onto the gap above or below another row to reorder it — or drop it into another branch to move it there. It can never be dropped inside its own branch. Dropping on the gap just below an open branch's row makes it that branch's first idea, right where the line is drawn, and dropping on the lower half of the top row adds it as that row's last idea, shown by a ring around the whole row instead of a line.
- Selection and collapse are shared. Clicking a row selects that node and the canvas pans to it;
selecting on the canvas highlights and scrolls to the row. The chevron collapses or expands a
branch on both surfaces, because it is the map's own collapsed state. It always does what the
row shows: a folded branch held open around the selected idea (or by a jump to a linked idea)
folds when you press Collapse, and stays folded. The canvas
/key and the phone Collapse button follow the same rule. - Every edit is a normal map edit — the same undo history, the same autosave, and the same save-conflict check as changing the node on the canvas. Ctrl+Z undoes an outline edit exactly as it undoes a canvas one.
- Resize it by dragging the divider between the canvas and the pane; the width is remembered for the session.
- One place the two surfaces differ on purpose: while the canvas is filtered by a find, the canvas shows only the hits and their branches, and the outline keeps showing the whole map. While a branch is focused, both show that branch.
Finding an idea (Ctrl+F)
- Open it with Ctrl+F (Cmd+F on a Mac) while the map has your keyboard, or tap Find in map on a phone. A find box opens at the top of the canvas. The key can be changed in Settings → Keyboard Shortcuts, where it is called Find in Mind Map.
- It matches an idea's text and its hidden note, ignoring capitals and accents. The count shows "2 of 7"; Enter and Shift+Enter, or the up and down arrows beside the box, step to the next and previous match.
- Filter hides every idea that does not match, keeping the branches the matches sit in. When nothing matches, the box says "No matches, filter paused" and Show all brings the whole map back.
- It searches only what is on screen. Inside a layer it searches only that layer, and inside a
focused branch only that branch; the box still reads "Find a node" (only a screen reader hears
"Find in this layer" or "Find in this branch"). It never looks inside other sub-maps, in a link's
web address, or in the names on task, board item and Vault note chips. So when it says
"No matches" but you can see the idea in a sub-map, open that sub-map first (
l), then press Ctrl+F there. Esc or the X closes it.
Focusing on one branch
A deep map keeps every other branch in the corner of your eye. Focus takes the rest away so you can work on one branch at a time.
- Enter it from the node's right-click menu (Focus on this branch), from the crosshair button on the toolbar with the node selected, or with Alt+Shift+B while the map has the keyboard. The centre node cannot be focused — that is the whole map.
- The canvas then shows that node and everything under it, and nothing else. The branch keeps its own shape and direction; it simply becomes the whole picture.
- A banner at the top names the branch and shows the chain of nodes from the map's centre down to it. Click an earlier name in that chain to widen the focus to that larger branch.
- A branch too tall for the screen starts at its top. The view keeps the readable zoom (it never shrinks the labels below the readable size) and opens with the branch's top idea just below the banner, so the banner never covers an idea. Scroll or drag down to see the rest. A branch that fits the screen is framed whole, as before.
- Leave with Escape, the X on the banner, or the same menu row and shortcut. You land back exactly where you were — the same zoom, the same place on the map.
- Everything you do inside focus is a normal edit — the same undo, the same autosave, the same notes, links and colours. A folded branch opens to show you its contents while focused, and stays folded in the map itself. Focus changes what you are looking at, never what is saved.
- At the top of the branch, Enter adds a child rather than a sibling, and the top node cannot be deleted, cut or have a parent inserted above it — the same rules the centre node follows.
- Find and the outline follow you in. A find only counts and steps through nodes inside the branch, and the outline lists that branch until you leave.
- Focus works in every flow direction, in the four-sided map, and on a phone, where the crosshair button sits on the toolbar.
Saving, and what happens when you quit mid-edit
- It saves itself. Every edit is written a moment after you stop, so there is no Save button to remember. If a save fails, the status next to the title says "Your mind map didn't save. Try again." and a notice appears; your work stays on screen, and the map is saved again the next time you change something. The chip says Saved only once your newest edit is written; while a newer edit is still waiting, it keeps saying it is saving. A failed save is kept and sent again on your next edit, when you open another map, when you pop the map out, or when the window closes, so switching maps no longer throws it away.
- Leaving a map never hides a refused save. If you switch to another map and the last save of the one you left is refused because an AI helper or another window changed it, you get a notice that your edit to it could not be saved, instead of nothing. Your copy is kept in that window until you close the app: open that map and press Undo to put it back. That Undo replaces the other changes, says so, and Redo brings them back. A failed save that is still kept when you reopen its map is shown on screen, so your next edit builds on it instead of replacing it; if someone else changed the map meanwhile, that next save is refused and you get the usual clash notice, never a silent overwrite of their change.
- A lost reply on the phone or web app is checked, not guessed. When the connection drops while a map saves, Omniscio reads the map back: if your edit is already there, it counts as saved and your next edit is not flagged as a clash.
- A leftover save from a closed window is judged by what the map holds. If the map already holds that edit, the copy is cleared quietly; if the edit was overtaken only by your own earlier save, it is sent again on top of it; otherwise you are told it could not be restored. A leftover save for a map that was deleted since is dropped after one notice instead of warning on every start.
- Someone else changing the map mid-typing: your words come back with Undo. If an AI helper, a second window or your phone saves the map while you are typing in a node, your words stay on screen while you type and you get one notice: "This mind map changed in another window or by an agent. Your edits are still here, but they were not saved. When you finish editing, the newer version loads, and Undo puts your copy back." When you finish the edit, the newer version (the AI's, or the other window's) loads over yours. Press Ctrl+Z straight away to bring your words back; that Undo replaces their change, and Redo puts it back. In the editor that Undo works only until you switch maps or close the app, so do it before you move on; after that, the next bullet is the way back.
- A clash that replaced your edits can be undone later. When a save clash swaps your version of the map for a newer one, Omniscio keeps a copy of your version on this computer, even across a restart. The next time you open that map, a notice offers Restore your version, which brings your edits back as one step you can undo. Undoing the swap yourself, or deleting the map, drops the copy.
- Signing out saves first. Before you sign out, Omniscio writes any edit still waiting to be saved and finishes creating a new map that is part-way through saving, while you are still signed in. If something still cannot be saved, you get a warning before the sign-out finishes.
- Renaming never fights a rename. Typing a new idea name in the outline, or a new map title, and then clicking away without changing it leaves the newer name alone instead of putting the old one back.
- Quitting mid-edit keeps the draft. Quit, restart or update while a note is open, or while an idea name is half-typed in the outline, and Omniscio writes that draft before it closes — the safety net no longer depends on the window being closed or reloaded. This covers a map open in the main window; a map popped out into its own window is still saved only when that window closes.
- At your plan's map limit, a new map waits instead of retrying. If your plan's map limit stops a new map from saving, you are told once, the map stays on screen marked as not saved, and Omniscio stops trying again on every edit. Delete another map and your next edit saves it; after an upgrade, the first edit made a minute or more later saves it. Pressing Try again, closing the window or signing out still tries to create the map right away.
- Undo and redo stay safe. After an undo, the highlight moves to an idea that still exists, so the next idea you add or paste can never attach itself to something you just removed.
Links to Mission Control, Tasks and the Vault
An idea on your map can become a real piece of work, or point at one that already exists, without you retyping it. The map never keeps a copy: the idea only remembers which task, board item or note it is tied to, and each of those apps stays the only place that changes its own data. Each action appears only while its app is switched on: Tasks for tasks, Mission Control for board items, the Vault for notes. These links are desktop only — the buttons, the chips and the link box's workspace section are not offered on a phone or in the web view, because the handlers behind them are desktop only.
- Turn an idea into a task or a board item. Right-click an idea and choose Make a task (Alt+Shift+D) or Make a board item (Alt+Shift+M; you pick the board). When the idea is already tied to one, the same row becomes Open task or Open board item and takes you there. Sub-ideas are not included; only the idea you picked. Pressing it again while the first one is still being made does nothing, and an idea that already has a live task pointing back to it gets that task again instead of a second one. Linking the idea to a different task removes the old task's "Mind map: ..." link, so making a task later never brings back a task you moved away from. If the idea is already linked to a live board item on the board you pick, Make a board item hands back that item instead of making a second one.
- Point at something that already exists. In the link box (Ctrl+L) the workspace section lets you pick an existing task, a board item or a Vault note. A Vault note opens inside Omniscio, not in your browser, and it keeps working after you rename or move the note in the app.
- An idea holds one board item. Picking a board item in the link box, or choosing Unlink on a board item chip that says it is gone, removes the links any other board items had to that idea. Those board items themselves are untouched, and tasks are not affected.
- Board items are yours to change. A Mind Map AI session cannot make a board item, link one to an idea, or rename one: make those changes yourself, on the map or on the board.
- Link the whole map to a board item. The toolbar's Link to Board Item button (a clipboard icon, available once the map has been saved) ties the map itself, not one idea, to a Mission Control item. The item's Links tab lists it under mind maps, separate from the Mind Map Ideas links made from single ideas, and every board item linked to the map shows as a chip beside the map's title in the editor header. See Mission Control, cross-entity linking.
- The other side leads back. A task made from or linked to an idea gets a "Mind map: ..." link in its context that opens the map with that idea selected, even when the idea sits inside a sub-map (an idea deleted since opens the map with "That idea is no longer in this map."). The link is added just after the task is made; if adding it fails, the task is still made without it and nothing tells you, so if a task has no "Mind map: ..." link, link the idea to that task again from the map. A board item gets a link of its own kind, Mind Map Ideas, that does the same.
- Chips show what is happening there. A tied idea wears a small chip: a checkbox for its task (done or still open; ticking it on the map completes the task), the board item's name, or the note's title. If the task, item or note was deleted, the chip says it is gone ("Task gone", "Board item gone", "Vault note gone") and offers Unlink. Two other cases are not deleted and never say gone: a note that lives in a different Vault from the one open shows "In another vault" with no Unlink (switch back to that Vault and the chip returns), and a board item on a board you are no longer a member of shows no chip at all while the tie stays on the idea. Unlink only a chip that says gone: Unlink clears the tie for good. A Vault note link shows only as its chip, never again as the corner link badge, and the chips sit along the node's bottom edge, just after its bottom-left corner badge. A live task or board item chip has an Unlink button beside it too: it clears the tie from the idea (for a board item it first removes the idea's link on the board, and if the board refuses, the idea keeps the item and you are told) and leaves the task or item itself alone. A task keeps its "Mind map: ..." link in its context; only clearing the tie from the command line drops that link. If an old board item link could not be removed while you link a different board item, you are told, the idea keeps its old board item, and choosing the new one again finishes the switch.
- Names stay in step. Rename the idea and its task and board item are renamed too; rename the task or item somewhere else and the idea picks up the new name while the map is open, or the next time you open it. The latest edit wins. A rename made by a Mind Map AI session renames the task only: the board item keeps its old name until you rename the idea yourself. A rename made while Tasks or Mission Control is switched off keeps your new name when that feature comes back on, as long as the app stays open; the task or item keeps its old name until you rename the idea again, and after a restart the old task or item name can replace the idea name again. Renaming an idea whose task was deleted shows no error.
- Deleting never deletes work. Deleting tied ideas with Delete (the key, the menu, the outline or the phone button) asks you first, and either way the task and board item are left alone. Cut does not ask (paste the idea back into the same map to keep its tie), and a Mind Map AI session that rewrites the map can remove tied ideas without asking — Undo brings them back while the map is open. Deleting a task or board item never deletes the idea. Deleting a whole map removes the board links that pointed at its ideas.
- Send map to Tasks (toolbar, while Tasks is on). The map's top idea becomes a parent task and its ideas become subtasks, up to 500 ideas in one send. Tasks nest at most 15 levels deep, so an idea deeper than that is placed alongside the deepest task above it. Only the top level is sent, even while a sub-map is open: ideas inside sub-maps are not, and the message says how many were left out. Ideas that already have a live task are skipped, so sending twice adds nothing. That holds even when the map lost its record of an earlier send: an idea whose live task still points back to it reuses that task.
- Map from a board or project plan. New > Map from a board or project plan builds a new map from a Mission Control board, with its groups and items; the items link back to their ideas when you can edit the board.
- Attach to a project as context. The toolbar's Attach to a project lets you attach up to five maps to a project. Any Claude session started in that project then reads those maps' current outlines, read fresh each time (sessions on other AI providers do not get them). Each map's outline is cut at about 8,000 characters, at a line break, with a note saying so; a map you deleted is skipped. The session shows a collapsed Mind Maps note at the top listing the maps it received, and names any attached map whose saved data could not be read. A session on another provider gets no maps, and the app log records that it was skipped.
- Vault search finds maps. The Vault's Ctrl+P search shows a Mind Maps group, matched on the map title and its ideas the same way note search matches — capitals, accents, the two ways an accented letter can be stored and non-breaking spaces are all ignored, and an idea is matched (and shown in the result) by the words the canvas displays, never its bold, code or link markup or a link's hidden address; type
kind:mindmapto search only maps. Picking one opens that map.
If a map goes missing
- A map you deleted. Deleting hides the map instead of erasing it, and the hidden row is cleaned up after your data-retention window — 30 days by default, and the same setting that trims old session logs, so shortening that shortens this too. There is no "Recently deleted" list and no undelete button yet, so the way back is to restore a whole-database backup taken before the delete (Local and cloud backups) — which rolls every other feature back to that point as well, making it the last resort rather than the first. Deleting a map also switches off every public share link made from it, at the moment you delete it: anyone you gave one of those links to finds it no longer opens the map.
- Keep a copy before a big edit. Export → JSON writes the whole map to a file, and Import reads it back in as a new map. Doing that before an AI session reorganizes a large map is the cheapest insurance there is. A re-imported map does not carry the original's task or board-item ties.
- An agent changed a map you have open. The open editor keeps the tree from before the change, so Ctrl+Z puts it back — but only until you switch maps or close the app. After that, the copy that saves you is an export you made beforehand.
- A map a sync replaced. When a newer copy of a map arrives from your other computer, it replaces the copy on this computer. The older version is kept as a hidden deleted map, named after the map with "(replaced by sync" and the date and time added, and it is cleaned up with other deleted maps after the data-retention window. There is no way to open it in the app yet, so the way back today is an Export → JSON you made beforehand, a whole-database backup taken before the sync (Local and cloud backups), or asking for help before the retention window ends. replaces the copy on this computer, and the version it replaced is kept as a hidden deleted map titled "<title> (replaced by sync <time>)" for the same data-retention window as a map you deleted. Like a deleted map it is not listed and has no undelete button yet, so the way back is a whole-database backup taken before the sync (Local and cloud backups), or an Export → JSON you made beforehand.
- A map that is listed but will not open. Its stored content no longer matches the current
format. The text itself is still in the local database file (the
mindmaps.datacolumn), which any SQLite tool can read — read-only, with Omniscio closed — because the app cannot repair it. Opening one says "This mind map is damaged and can't be opened. Trying again won't help, but you can delete it from your list of maps." Do not delete it if you want its words back: deleting starts the clock on the hidden copy (above). - There is no recovery screen yet. Bringing back a deleted map, a map a sync replaced, or the text of a map that will not open all mean working with a backup or the database by hand. Ask for help as soon as you notice: hidden copies are erased for good once the data-retention window passes (see Reporting a problem with a map below).
- "Couldn't render this map." The canvas shows this card in place of the map in three cases. The map data looks corrupted means the saved tree is broken (no ideas, two ideas with one id, an idea whose parent is missing, or a loop); undo helps only when your own last edit caused it. More than 2,000 ideas means the map is over the size Mind Map can show; nothing is damaged. Something went wrong while drawing this map means the drawing step crashed and the data is safe. Each card shows a Reference ID with a copy button, and Report this opens a bug report that already carries that reference and the map id, which match the line in the app log.
When something goes wrong: messages you might see
Search this page for the words you see on screen. Each message is quoted by its opening words, and a … stands for the part the app fills in (a number, a limit or a name). Save messages are under Saving, and what happens when you quit mid-edit above, and the "Couldn't render this map." card is under If a map goes missing. If a message is not here, or the step does not help, see Reporting a problem with a map below.
Opening a map or a link
- "That mind map no longer exists." The link points at a map that was deleted, or at a map that belongs to another account. Look for it in your saved-maps list.
- "That idea is no longer in this map." The map opened, but the idea the link pointed at was deleted.
Importing a file or an outline
- "That file is not a valid mind map. If it is a text outline, paste it with New > Import outline instead." The file is not a map Omniscio saved. A text outline goes in through New > Import outline.
- "That spreadsheet needs either id and parent_id columns, or Level 1, Level 2 (and so on) columns." Rename the header row to one of the two layouts:
id,parent_idandlabel, orLevel 1,Level 2and so on (see CSV and Excel in part 2). - "That spreadsheet has no rows to turn into ideas." Every row was blank.
- "A spreadsheet may have at most … ideas." (also "An outline may have at most …" and "A mindmap may have at most … nodes.") Split the file and import it in parts.
- "That spreadsheet could not be read. Save it as .csv or .xlsx and try again." Old
.xlsfiles and damaged workbooks cannot be read. - "That file is not saved as UTF-8 text. Save it as UTF-8 and try again." In Excel, use Save as > CSV UTF-8.
- "That file is too large to import (max … MB)." or "That outline is too large to import. The limit is … characters." Import it in parts.
- "That does not look like a Mermaid mindmap." A Mermaid mind map starts with the line
mindmap. - "A node label may be at most … characters." Shorten that label, or move the extra words into the idea's note after the import.
- A notice listing rows from a spreadsheet (rows with a missing parent, a repeated id, no id, or text that was shortened). It names up to 10 rows of each kind, then says how many more. A row with no id and no text, note or link at all is skipped without being listed.
AI (Expand and Generate)
- "Mind Map's AI suggestions need Omniscio credit or your own AI key. Add credit under Plan & Usage, or add a key in Settings." Do one of those, then try again.
- "Mind Map has reached today's AI limit. It resets tomorrow, or you can raise the limit in Settings." Wait until tomorrow, or raise the limit. While your plan is not recognized yet, the same message says the free plan's limit instead of today's.
- "The AI account Mind Map uses refused this request: its key was rejected or it is out of credits. Check the key or add credits in Settings." Fix the key or add credits; trying again first will not help.
- "Mind Map couldn't reach the AI service. Check your internet connection, then try again." You are offline.
- "The AI service is busy right now. Wait a minute, then try again.", "The AI took too long to answer. Try again." or "Another AI request is still running. Try again in a moment." Wait, then try again.
- "The AI did not suggest any ideas. Try again." or "The AI did not return a usable outline. Try again." Reword the idea or topic, then try again. Each try is charged.
- "The AI request could not be completed. Please try again." or "Could not expand that idea." Try again once. If it keeps happening, report it.
Exporting and sharing
- "Could not render the map image. Very large maps can be too big to draw. Try again, or export as JSON or Markdown instead." The map is too big for one picture.
- "The map is still loading. Try exporting the image again in a moment." or "Nothing to export yet." Wait for the map to appear, or add an idea first.
- "Could not export the image." The picture could not be saved. Try again, or pick another folder.
- "Could not create the share link." Share needs an internet connection. When the app cannot check for the map's earlier link, it stops here instead of making a second public link. Check your connection and try again.
- "This map is too large to share. Remove some ideas or long notes, then try again."
- "The link was published, but this map could not keep track of it." The link works, but deleting the map will not turn it off. Remove it in Shares when you no longer want it public.
Tasks, board items and Vault notes
- "Couldn't update the linked task or board item with the new name." Rename the idea again, or rename the task or item in its own app.
- "Couldn't make the board item. Check that Mission Control is connected and try again." When the connection is the problem the message says it could not reach Mission Control instead, and when the board refuses the item it says the board did not accept it. Fix what the message names, then try once more.
- "The board item was made but could not be linked to this idea, and it could not be removed. It is still on the board: link it to the idea or delete it there."
- "The board item was made, but this board has not finished syncing to this computer, so it is not linked to this idea yet. Once the item shows on the board, link it to this idea." Wait until the item shows on the board, then link it.
- "That task no longer exists." or "That board is no longer available." It was deleted, or you lost access to the board.
- "This mind map is already being sent to Tasks. Please wait a moment."
- "None of the … ideas could be sent to Tasks." or "Couldn't send any of those ideas to Tasks. Try again." Send again: ideas that already became tasks are skipped.
- "Set up your Vault first to link a note.", "No notes found" or "Couldn't search your Vault notes. Please try again." in the Vault note picker. Set up the Vault, try other words, or try again.
Reporting a problem with a map
Export & share → Report a problem with this map opens the bug report form with a first line
that names the map: its title, map id, idea count, last-saved time and save state, plus the app
build. Support uses the map id to find the map's lines in the app log, which a bug report
includes by default. To send the map itself, export it first (Export → JSON) and attach the
file. Mermaid (.mmd, .mermaid) and Excel (.xlsx) files that fail to import can be attached
to the report too.
Related
- Mind Map part 2 — hidden notes, layers, look and layout, importing and sharing, the AI features, touch, and building a map with the mind-map skill.
- mermaid-diagrams.md — the same shared diagram engine, drawing a map as text.
- tasks-v2.md and mission-control.md — where an idea's task or board item lives.
- kms.md — the Vault, where a linked note lives and where Vault search finds your maps.
- mind-map skill — the bundled skill that builds a map from a conversation.
Related — Omniscio’s unreleased-feature
- Omniscio’s unreleased-feature (“Lab”) gate — how a feature built ahead of release is kept hidden, then revealed and eventually shipped. Mind Map is still a lab feature, but one that is on for every install, so its row sits in Settings → Features → Mind Map rather than behind an opt-in.
Speed cost
What having Mind Map switched on costs the app, measured Nov 6, 2026 on a test copy of the app. Each number is the middle of three rounds, with Mind Map on and off (Settings → Features → Mind Map) run in alternating order on fresh test copies of the app.
| Measure | Mind Map off | Mind Map on | Cost |
|---|---|---|---|
| App startup (launch to dashboard ready) | 5.7 s (5.6 to 7.1) | 6.3 s (5.7 to 7.5) | none measurable: the two ranges overlap |
| Memory, whole app, 15 s after startup | 4,236 MB | 4,236 MB | none measurable |
| Download size (Mind Map's own screen code) | not loaded | 214 KB (73 KB compressed) | loaded only when Mind Map is first opened |
| Open a 500-idea map | not available | 0.44 s (0.41 to 0.51) | only when a map is opened |
- Why startup and memory do not move: Mind Map's screens load only when you first open it, so having it switched on does not slow startup or use extra memory.
- On the same build: a 500-idea map painted in 1.2 s and a 2,000-idea map in 2.6 s (budgets 30 s and 90 s); on 2,000 ideas a pan answered in 1.2 s and a zoom in 0.14 s; a 20,000-idea map spread over layers saved in 2.6 s; importing a 2,000-line outline took 0.06 s; opening a 2,000-idea map grew the main process by 36 MB and left the screen process at 72 MB. On a build from the same day, creating 100 ideas by keyboard took 10.0 s, deleting them 3.4 s, and a search across 2,000 ideas answered in 0.9 s. Typing speed on a 2,000-idea map and undoing 100 creates were not measured (both are known gaps and will be added when they can be measured).
Last verified 2026-11-20