TableProApp · datlechin · Aug 22, 2026 · Aug 22, 2026
diff --git a/docs/customization/notifications.mdx b/docs/customization/notifications.mdx
@@ -5,6 +5,11 @@ description: Which finished operations notify you, how long work has to run firs
 
 You only get told when the result is somewhere you are not. That means TablePro behind another window or in another Space, the window minimized, or the tab that ran the work not the one on screen. Work you cancelled yourself never notifies, and neither does anything that finished faster than the threshold.
 
+<Frame caption="The Notifications tab in Settings">
+  <img className="block dark:hidden" src="/images/settings-notifications.png" alt="Notifications settings tab" />
+  <img className="hidden dark:block" src="/images/settings-notifications-dark.png" alt="Notifications settings tab" />
+</Frame>
+
 **Settings > Notifications** changes any of it.
 
 | Setting | Default | Covers |

diff --git a/docs/customization/settings.mdx b/docs/customization/settings.mdx
@@ -5,6 +5,11 @@ description: Every settings tab, its controls, and their defaults
 
 The settings window is app-wide: a value on any of these ten tabs holds for every connection you open. `Cmd+,` opens it; what belongs to one connection is in that connection's form instead.
 
+<Frame caption="The settings window">
+  <img className="block dark:hidden" src="/images/settings-window.png" alt="Settings window" />
+  <img className="hidden dark:block" src="/images/settings-window-dark.png" alt="Settings window" />
+</Frame>
+
 <CardGroup cols={2}>
   <Card title="General" icon="gear" href="/customization/general-settings">Language, startup, tabs, sidebar, query timeout, updates, reset.</Card>
   <Card title="Appearance" icon="palette" href="/customization/appearance">Appearance mode, themes, per-theme fonts and colors.</Card>

diff --git a/docs/external-api/tokens.mdx b/docs/external-api/tokens.mdx
@@ -5,6 +5,11 @@ description: Token model, scopes, connection allowlists, expiry, revocation, and
 
 **Read Only** is where the **Generate Token** sheet starts, and it is the right level for a client that only reads. Move to **Read & Write** when an agent has to change data, and to **Full Access** only for `DROP` and `TRUNCATE`, which nothing below it can reach. The plaintext is shown once at creation and never again; what persists is a salted SHA-256 hash in the login keychain.
 
+<Frame caption="The MCP tab in Settings">
+  <img className="block dark:hidden" src="/images/mcp-tokens.png" alt="MCP tokens" />
+  <img className="hidden dark:block" src="/images/mcp-tokens-dark.png" alt="MCP tokens" />
+</Frame>
+
 ## Permission levels
 
 | Level | Scopes | What it can do |

diff --git a/docs/features/code-folding.mdx b/docs/features/code-folding.mdx
@@ -5,6 +5,11 @@ description: Collapse statements, CTEs, subqueries and BEGIN blocks in the SQL e
 
 Move the pointer into the gutter and chevrons appear. Every region that spans more than one line gets one, which covers whole statements, table bodies, CTEs, subqueries, `BEGIN` blocks and block comments. Click to collapse, click again to expand.
 
+<Frame caption="A folded region and its chip in the gutter">
+  <img className="block dark:hidden" src="/images/code-folding.png" alt="Code folding in the SQL editor" />
+  <img className="hidden dark:block" src="/images/code-folding-dark.png" alt="Code folding in the SQL editor" />
+</Frame>
+
 The chevron points down while the region is showing and right while it is folded, the way a disclosure control behaves everywhere else in macOS. Resting on one marks how far its region reaches. Where a statement and the block inside it open on the same line, the chevron folds the larger of the two.
 
 A folded region keeps its chevron whether or not the pointer is in the gutter, so nothing is hidden without a visible way back. Move the pointer away from a gutter with nothing folded and it is line numbers again.

diff --git a/docs/features/query-results.mdx b/docs/features/query-results.mdx
@@ -7,6 +7,11 @@ import RowCap from "/snippets/row-cap.mdx";
 
 Every statement you run gets its own result tab. The next run reuses an unpinned one rather than adding to the pile, so a tab survives only as long as you leave it unpinned.
 
+<Frame caption="Result tabs above the grid">
+  <img className="block dark:hidden" src="/images/query-results.png" alt="Query result tabs" />
+  <img className="hidden dark:block" src="/images/query-results-dark.png" alt="Query result tabs" />
+</Frame>
+
 ## Naming
 
 A result is named after the table it came from. When there is no single table, the statement names itself, and a line comment written above the statement wins over the SQL:

diff --git a/docs/images/code-folding-dark.png b/docs/images/code-folding-dark.png
diff --git a/docs/images/code-folding.png b/docs/images/code-folding.png
diff --git a/docs/images/mcp-tokens-dark.png b/docs/images/mcp-tokens-dark.png
diff --git a/docs/images/mcp-tokens.png b/docs/images/mcp-tokens.png
diff --git a/docs/images/query-results-dark.png b/docs/images/query-results-dark.png
diff --git a/docs/images/query-results.png b/docs/images/query-results.png
diff --git a/docs/images/settings-notifications-dark.png b/docs/images/settings-notifications-dark.png
diff --git a/docs/images/settings-notifications.png b/docs/images/settings-notifications.png
diff --git a/docs/images/settings-window-dark.png b/docs/images/settings-window-dark.png
diff --git a/docs/images/settings-window.png b/docs/images/settings-window.png