Settings are stored with Chrome (chrome.storage.sync) and never sent to TechFabric or anyone else.
Match Databricks reads the workspace page's font and colours at run time (computed style only) and falls back to neutral colours and Roboto when it cannot. On this options page, the popup and the side panel there is no workspace page to read, so they show the neutral version. The card size (Compact 320 / Comfortable 420 / Wide 640) is chosen in the card's menu or by dragging its edge, and is remembered per kind of page.
The results grid lives on those pages, so the card stays out of the way until you ask for it. Open, it is at most 45% of the window high and 320 px wide there (70% and 360 px elsewhere). Its position and dock stay remembered per kind of page.
Drag the tab or the panel header to move it; it snaps to the nearest edge and is remembered. (applies to the open tab on a supported site)
The 3-step first-run tour is remembered on this computer only (chrome.storage.local).
The pattern is a case-insensitive part of the workspace host name, or a /regex/. Colors: red, orange, yellow, green, blue, purple, gray or #rrggbb. Without rules no banner is shown.
For AWS/GCP workspaces, include ?o=<workspace id> so deep links keep the right workspace.
Start each snippet with -- @name Title (optional -- @group Name). Placeholders: {{catalog}} {{schema}} {{table}} {{table_fqn}} {{schema_fqn}} {{volume_fqn}} {{function_fqn}} {{table_fqn_raw}} {{host}} {{job_id}} {{run_id}} {{pipeline_id}} {{warehouse_id}} {{cluster_id}} {{endpoint}} {{model_fqn_raw}}.
Only endpoint names are stored (in Chrome sync storage). The extension never calls these endpoints; it only writes them into the text it generates.
With a workspace connected, the Now tab shows live details for the page you are on: table owner and columns, recent job runs, the decoded error of a failed run, running compute, and a one-click Delta health check. The extension only reads (it never changes anything), calls only the workspace you are on, and sends nothing from it to TechFabric or anyone else. Connect from the Now tab on any table, job, run, cluster, warehouse, pipeline or endpoint page.
Sign-in: browser session uses your Databricks sign-in as it is. If a workspace does not accept it for the REST API, use a personal access token (Settings > Developer > Access tokens; give it a short lifetime). Tokens are kept on this computer only (chrome.storage.local), never synced, and sent only to the workspace they were saved for.
The Ask button (sparkle icon) answers Databricks questions. It uses two sources, each off until you turn it on:
No workspace is connected yet.
"Notify me when it finishes" on a running job run shows a desktop notification when it ends. The run is checked every 30 seconds by an open tab of that workspace (no tab open: the check waits until you open one). Watches end after a day.
Feedback is sent only from the feedback sheet (the thumbs under answers and diagnoses, or ⋯ > Send feedback), which shows exactly what goes to databricks.techfabric.com first. Your words are scrubbed of emails, tokens, paths and IDs. This list stays on this computer.
Nothing sent yet.
Airlift is TechFabric's governed migration factory for Databricks. It runs as a Databricks App in your workspace. Enable this module to link Databricks objects to Airlift records, open Airlift pages and run a read-only readiness check. Off by default. The address and non-secret IDs are stored only in this browser (chrome.storage.local); no token, password or secret is ever stored. Requests go only to the address you enter, using your existing sign-in session, and only when you click a button.
https://airlift-123456.7.azure.databricksapps.com), then Save.Off until you turn it on. When on, the card can show one calm Heads-up at a time (for example "This run failed" with a button that opens the triage helper) and the toolbar icon shows how many hints are active on the current tab. Hints never run anything, never send anything and never open a page by themselves.
Without this, only hints that need no page content work (PROD workspace, risky SQL you just copied with this extension). With it, the extension reads the few facts listed below, locally, and nothing else. The card menu has "Hints on this page", which shows exactly what was read right now.
Values are on or off; alerts is the master switch for that workspace, pagehints the page readers, the other names are the types above. Not listed = the global setting.
None.
(kept in chrome.storage.local on this computer)
These choices are stored now so the settings do not change later. In v0.7 no notification is ever created and no extra permission is requested; adding notifications in v0.8 will ask for the browser's notification permission at that point.
Used only to scale the estimate in the SQL that the cost explainer writes. The queries read system.billing tables, which are often present but depend on the workspace, the edition and your permissions (they were readable on Databricks Free Edition when tested); the output starts with an availability check and offers a fallback.
The toolkit can remember catalog, schema, table and column names so its dropdowns and SQL suggestions know your objects. They are stored only in this browser (chrome.storage.local, never synced, never sent anywhere), per workspace host, as names only: no rows, no SQL, no tokens. Names come from the address / title of pages you open with the card, from names you paste into the toolkit, from single names you copy with its buttons, and from results you paste into "Object names" yourself. The toolkit never queries Databricks.
Loading...
Export your settings and custom snippets as a JSON file to back them up or share them with your team. Import only reads known settings; nothing is executed.
(opens chrome://extensions/shortcuts)
Share this tool · Need help with Databricks, data or AI? Talk to TechFabric
No analytics, no remote code, no accounts. The extension reads the URL/title of supported pages locally to build links. It makes no network requests of its own, except these opt-in features: Live workspace (reads details of the page you are on from that same workspace's REST API, read-only), AI from your workspace (a chat model in that workspace, through Databricks AI Gateway), Ask the Field Guide (sends your question, with emails, tokens and paths removed, to databricks.techfabric.com), Send feedback (only when you press Send, after showing exactly what goes, to databricks.techfabric.com), Notify me when it finishes (checks a run you chose in that workspace) and the Airlift module. Nothing else is ever sent to TechFabric: no workspace data, no analytics. Generated text (SQL, Python, notebooks) is built in your browser from what you type or paste; notebook files are saved with a local download.