Three steps to full access.
Get the extension
GNKG installs from the Chrome Web Store. Add it to Chrome, sign in at notebook.google.com and the HUD turns green. The listing is in review; this page will carry the Add to Chrome button the moment it is approved.
Open the console
Click the GNKG icon → Open console (side panel), or use the Console page — it goes LIVE automatically when the extension is present.
Give your agents the bridge
Run the one-line installer on the Agents page (writes MCP configs for Claude Desktop, Claude Code, Cursor, Windsurf and Codex, installs the /gnkg skill), or add the bridge by hand with npx -y @metaphyllc/gnkg-bridge. The extension auto-connects to ws://localhost:7801/extension.
Install and Use (Page-Visitor Instructional)
A. Load the extension. Open chrome://extensions, enable Developer mode, choose Load unpacked and select the extension/ folder. Pin GNKG. Open https://notebooklm.google.com and sign in; the HUD in the bottom-right corner turns green when the session tokens are captured.
B. Open the console. Click the GNKG icon → Open console (side panel). Refresh notebooks, select one, add a URL or paste text, generate a Studio artifact, ask a question, build the graph.
C. Run the pump. Pump tab → Choose folder → Plan bins (FFD) → inspect Bin 0 → Push to "notebook". Watch the Jobs & Log tab. Set a rolling window in Settings if the corpus exceeds your plan's source cap.
D. Give Claude full access. In mcp-bridge/: npm install, then add to Claude Code:
{ "mcpServers": { "gnkg": { "command": "node", "args": ["C:/…/gnkg/mcp-bridge/server.js"] } } }
The extension auto-connects to ws://localhost:7801/extension; gn_health confirms the lane. OmniLad or WCRS can use the REST twin at http://127.0.0.1:7802/api/<tool> (for example POST /api/gn_create_artifact).
E. Use the Console page. The console on the site is the same component as the side panel. With the extension installed it runs live; without it, it runs the simulator — a faithful in-memory Gemini Notebook that lets you plan bins, build graphs and rehearse the workflow before you touch a real notebook.
“The bridge was never the server. The bridge was the session.”