Spellbook Data Catalog

Research preview

The Spellbook Data Catalog is in research preview. The hosted console is currently offline while we harden it; today it runs as a local preview on your machine, available on the Scale plan. Expect rough edges, and expect this page to change. What’s written below describes what works today.

The Data Workers Spellbook Data Catalog is the human control plane over the swarm: the browser surface where your team sees what the agents know, watches what they’re doing, approves what they propose, and browses the estate the fleet maintains.

It is deliberately not another system-of-record catalog to maintain by hand. The agents do the cataloging; the Spellbook is where humans stay in command — the receipt surface for the fleet’s actions.

What it does today

• Estate browsing — tables, schemas, lineage, and quality signals from your connected systems, searchable.
• Connector management — register a system through a credential form, test it live, see its true 🟡/🟢/🔴 state. A “Paste schema / CSV” path covers systems without a connector.
• Agent activity & approvals — watch runs, review proposed writes, approve or reject with the change and blast radius shown.
• Onboarding wizard — a guided first-run flow that gets a first system connected and verified from the browser.

How it’s built (30 seconds, but it matters for security)

Split-brain: the UI is a static page; the brain — the agents, all credentials — runs on your machine via the local launcher on localhost:4747. The browser talks to your own machine. We are not a SaaS that ingests your data — no credentials, warehouse data, query results, or PII touch our servers. Tell your security team this first; details in How your data is handled.

Running it

Scale plan, with your customer npm token:

npm config set //registry.npmjs.org/:_authToken=<your-customer-token>
npx @dataworkersproj/agent-console@latest serve --local-ui

The full walkthrough is in the pilot onboarding track.

What research preview means here

• The hosted console site is offline; local preview is the supported path.
• Some views run on sample data until their backing system is connected and verified — the console never blends the two silently: sample data is labeled.
• Console SSO/SAML/SCIM are not self-service; identity for the browser surface is part of the Enterprise “set up with us” conversation.
• The local launcher needs Node and your npm token, so today a data steward without a dev setup reviews approvals in a shared session with an engineer — a hosted console for non-engineers is exactly what research preview graduates into.
• The console’s connector card list is a subset of the full connector set — anything missing still connects via environment variables in the terminal path.

Found something broken or missing? That feedback directly shapes what graduates out of preview.