Notebook Intelligence is live · free · last verified 8 Nov 2026 · viability monitor
Notebook Intelligence
Notebook Intelligence runs agentic AI coding — Claude Code, Copilot, and Ollama — directly inside JupyterLab 4 notebooks.
If your work already lives in JupyterLab 4, NBI is the most complete agentic assistant available inside it: Claude Code sessions with status cards and inline diffs, Skills, Plugins, and MCP servers, plus provider, model, and endpoint policy admins can actually enforce. The free, open-source model removes the budget objection entirely. The catch is narrowness — no JupyterLab 4 means no NBI, and if you live in VS Code or want a standalone agent IDE, there is nothing here for you.
Verdict generatedVerified 6d ago · liveness 68/100 · cite: rightaichoice.com/tools/notebook-intelligence
- Data scientists running agentic AI coding inside JupyterLab 4 notebooks
- Platform teams needing enforceable provider, model, and endpoint policy on managed JupyterHub
- Developers extending the assistant with custom MCP servers, Skills, and Plugins
- Air-gapped or privacy-sensitive research teams running local models through Ollama
- Anyone working outside JupyterLab 4 — the extension requires it
- Users who want a standalone AI coding editor like Cursor or VS Code Copilot
- Casual users after zero-config autocomplete with no provider or policy setup
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Notebook Intelligence if you don't work in JupyterLab 4 or don't want to pick a provider and model — it's an extension for notebooks you already run, not a standalone editor.
You pay your model provider separately — NBI is the free extension, but Claude Code, Copilot, or an API endpoint still bills you per usage.
NBI is an open-source JupyterLab extension and carries no licence fee itself, which puts it below paid notebook assistants and standalone agent IDEs on software cost. Your real budget line is the model provider you route through it — Claude Code, GitHub Copilot, or an OpenAI/LiteLLM-compatible endpoint — plus the GPU capacity behind Ollama if you run local. For a platform team already paying for JupyterHub, that trade is usually favourable.
In short
Notebook Intelligence — Notebook Intelligence runs agentic AI coding — Claude Code, Copilot, and Ollama — directly inside JupyterLab 4 notebooks. Best for Data scientists running agentic AI coding inside JupyterLab 4 notebooks, Platform teams needing enforceable provider, model, and endpoint policy on managed JupyterHub, Developers extending the assistant with custom MCP servers, Skills, and Plugins. Free to use.
What is Notebook Intelligence?
Notebook Intelligence — Notebook Intelligence runs agentic AI coding — Claude Code, Copilot, and Ollama — directly inside JupyterLab 4 notebooks. Best for Data scientists running agentic AI coding inside JupyterLab 4 notebooks, Platform teams needing enforceable provider, model, and endpoint policy on managed JupyterHub, Developers extending the assistant with custom MCP servers, Skills, and Plugins. Free to use.
Notebook Intelligence (NBI) is an open-source extension that drops an agentic AI coding assistant into JupyterLab 4. Its centerpiece is Claude Code: a chat sidebar that holds up during long agent turns, because tool calls show up as persistent status cards with inline diffs telling you exactly which cell is being rewritten. Version 5.0 made that sidebar agent-aware, syncing open files as the agent changes them on disk. You're not locked to one vendor. NBI also drives GitHub Copilot — including Codex chat models routed through the correct Copilot endpoint — Ollama for local models, and any OpenAI- or LiteLLM-compatible endpoint. Trigger it from the sidebar or inline on any cell with Cmd+I/Ctrl+I, and agent mode will create, edit, and run cells to repair its own errors. Coding-agent CLIs now launch straight from the JupyterLab launcher, while cell output actions give you one-click Explain, Ask, and Troubleshoot. Administration is where NBI leaves hobby extensions behind. Skills, MCP Servers, and Plugins each sit in their own top-level Settings tab (as of the 5.1.0 line) and each carries a force-on, force-off, or user-choice policy. Environment variables let admins pin provider, model, and endpoint across a managed JupyterHub deployment, and organization-wide Skills manifests sync down to every user. It's built for people whose work already happens in a notebook — data scientists, researchers, and platform teams — not for developers shopping for a standalone AI editor.
Key features
- Chat sidebar with persistent tool-call status cards and inline diffs
- Agent-aware sidebar that syncs open files as the agent edits on disk
- Inline chat on any code cell via Cmd+I/Ctrl+I
- Agent mode that creates, edits, and runs cells autonomously
- Claude Code integration with sessions, Skills, and Plugins
- GitHub Copilot chat and completion, including Codex chat models
- Ollama local model support for offline and air-gapped notebooks
- OpenAI-compatible and LiteLLM-compatible endpoint support
- Coding-agent CLI launcher tiles in the JupyterLab launcher
- MCP server management for custom tools, databases, and APIs
- Skills, MCP Servers, and Plugins as top-level Settings tabs with admin policies
- Custom spinner verbs for agent activity
- MCP stdio-command allowlist for tool-call security
- Filesystem token-password check for file access control
- Admin enforcement of provider, model, and endpoint via environment variables
Behind the verdict
NBI earns its place by respecting a constraint most AI coding tools ignore: some people never leave the notebook. Rather than bolting autocomplete onto a cell, it makes the notebook itself agent-aware. Pick this when your team already runs JupyterLab 4 and you want agentic coding without a second environment. The Claude Code sidebar is the strongest single reason — status cards with inline diffs make long agent turns legible instead of a spinner and a prayer, and the 5.0 file-sync keeps the notebook honest about what's changing on disk. The admin controls are the quiet differentiator. If you run a managed JupyterHub, pinning provider, model, and endpoint via environment variables is the kind of thing that gets an extension past security review. Skills, MCP, and Plugins each getting a policies tab matters more than it sounds. Pass if you don't run JupyterLab 4. That's the hard boundary, and it won't bend. Casual users who want zero-config autocomplete will also bounce off the provider and policy setup, and anyone in VS Code or JetBrains should stay there. Against a standalone agent IDE like Cursor, NBI loses on breadth and polish. What it wins is location — the assistant lives where the analysis runs, with the data and kernels in reach. For a research or platform team, that's often the whole argument. One caveat worth flagging: the fast release cadence (5.0 to 5.1.0 in weeks) cuts both ways — current, but pin your version before rolling it out across a managed deployment.
Models under the hood
as of 2026-11-09
Limitations
- Notebook Intelligence is an open-source JupyterLab 4 extension rather than a hosted app, so it requires a JupyterLab environment you run or your platform team manages.
- It ships no models of its own — you bring Claude Code, GitHub Copilot/Codex, or Ollama, plus any OpenAI- or LiteLLM-compatible endpoint.
- Skills, MCP servers, and Plugins each require configuration and may be locked down by admin policy, so what you can change depends on how your deployment is set.
- It does nothing for you outside JupyterLab 4.
as of 2026-10-07
Researching Notebook Intelligence? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Notebook Intelligence still active?
Notebook Intelligence is live · free · last verified 8 Nov 2026 · viability monitor.
Viability score
How well maintained and how widely used is Notebook Intelligence? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What's new in Notebook Intelligence
Checked 9 days agoAcross the latest 4 updates: 4 feature updates.
NBI 5.1.0: tool-call status cards, custom spinners, security guardrails
Claude agent tool calls now render as persistent status cards with inline diffs. Adds custom spinner verbs, an MCP stdio-command allowlist, and a filesystem token-password check.
Coding-agent launchers, Codex support, security hardening
Coding-agent CLIs can now be launched from the JupyterLab launcher. Codex chat models use the correct Copilot endpoint, alongside accessibility and security passes.
Agent-aware chat sidebar in NBI 5.0
The chat sidebar keeps users informed during long Claude turns and syncs open files with the changes the agent makes on disk.
Skills, MCP, and Plugins promoted to top-level Settings tabs
Each of the three features gets its own top-level Settings tab with force-on, force-off, or user-choice admin policy for easier management.
What do users say about Notebook Intelligence?
What people actually say about Notebook Intelligence — is it worth it?
Our community sentiment research written Jul 6, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Notebook Intelligence — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 8 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Notebook Intelligence 14 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed features, description, summary, our verdict, pricing tiers, who it suits
- — changed switching out, use cases, description, summary, our verdict, who should skip it, setup time, hidden costs, pricing fit, limitations, pricing tiers, switching in, features
- — changed SSL certificate
- — changed summary, who it suits, features, pricing tiers, who should skip it, our verdict, description
- — changed limitations, models, platforms
- — changed who it suits, switching out, who should skip it, use cases, switching in, hidden costs, pricing fit, setup time, features, our verdict, description, summary, models
Showing the 6 most recent of 14 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Notebook Intelligence cost in 2026?
Notebook Intelligence: Free to use. Pricing last verified 8 Nov 2026.
Plans compared
Every published Notebook Intelligence tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Free | Free | — | Data scientists, research groups, and platform teams running JupyterLab 4 who already pay for a model provider or run local models.Adds: Starting tier — open-source extension with no licence fee; you supply Claude Code, Copilot, Ollama, or an OpenAI/LiteLLM-compatible endpoint. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Notebook Intelligence's pricing actually pencils out — and where peers do it cheaper.
NBI is an open-source JupyterLab extension and carries no licence fee itself, which puts it below paid notebook assistants and standalone agent IDEs on software cost. Your real budget line is the model provider you route through it — Claude Code, GitHub Copilot, or an OpenAI/LiteLLM-compatible endpoint — plus the GPU capacity behind Ollama if you run local. For a platform team already paying for JupyterHub, that trade is usually favourable.
Has Notebook Intelligence's pricing changed?
No plan price for Notebook Intelligence has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Notebook Intelligence?
Pick Notebook Intelligence if you are Data scientists running agentic AI coding inside JupyterLab 4 notebooks, Platform teams needing enforceable provider, model, and endpoint policy on managed JupyterHub, Developers extending the assistant with custom MCP servers, Skills, and Plugins, Air-gapped or privacy-sensitive research teams running local models through Ollama.
Look elsewhere if you are Anyone working outside JupyterLab 4 — the extension requires it, Users who want a standalone AI coding editor like Cursor or VS Code Copilot, Casual users after zero-config autocomplete with no provider or policy setup, Teams standardised on VS Code, JetBrains, or a web-only IDE.
Skip it if Skip Notebook Intelligence if you don't work in JupyterLab 4 or don't want to pick a provider and model — it's an extension for notebooks you already run, not a standalone editor.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Notebook Intelligence actually fits — and what changes day-one when you adopt it.
You open the NBI chat sidebar, point Claude Code at the failing cell, and watch tool calls arrive as persistent status cards with inline diffs as it rewrites the code.
Outcome: The fix lands in the notebook with a visible diff for each edit, so you can accept or revert without guessing what the agent touched.
You pin the provider, model, and endpoint through environment variables and set Skills, MCP Servers, and Plugins to force-on, force-off, or user-choice in the top-level Settings tabs.
Outcome: Every researcher gets the same sanctioned assistant config, and org-wide Skills manifests sync down without per-user setup.
You point NBI at a local Ollama model and use inline chat on cells with Cmd+I/Ctrl+I, with no traffic leaving the network.
Outcome: Agentic code help stays inside the enclave, including the security guardrails — MCP stdio-command allowlist and filesystem token-password check.
Use cases
- Chat with Claude Code inside JupyterLab to debug code without leaving the notebook.
- Use inline chat to generate and edit code cells with natural-language prompts.
- Run agent mode to execute and fix notebooks from a high-level description.
- Connect local Ollama models for fully offline AI coding assistance.
- Supervise long agent turns via persistent tool-call cards and inline cell diffs.
- Launch coding-agent CLIs directly from the JupyterLab launcher.
- Lock provider, model, and endpoint choices across a managed JupyterHub deployment.
- Distribute Skills and MCP configuration to every user via synced manifests.
Setup time & first value
How long it actually takes to get something useful out of Notebook Intelligence — broken out by persona, not the marketing-page minute.
Installing the extension into an existing JupyterLab 4 environment is quick; first useful output can come in minutes if you already have Claude Code or Copilot credentials. Budget longer for the admin path: pinning provider, model, and endpoint via environment variables and setting Skills, MCP Servers, and Plugins policies across a managed JupyterHub is a configuration project, not a five-minute
Switching to or from Notebook Intelligence
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual notebook editing: install the extension, connect Claude Code or Copilot, and use inline chat on cells you'd otherwise rewrite by hand.
- →From standalone AI editors: keep the agent behaviour but move the context back into the notebook where the data and outputs already live.
- →From Jupyter AI or similar notebook assistants: route the same notebook workflow through NBI's Skills, MCP Servers, and Plugins tabs.
- →From local-only scripting: add Ollama as the provider to bring model inference back onto your own hardware.
- ↗To a standalone agent IDE such as Cursor or VS Code Copilot: move out when your work shifts from notebook-centric to repo-centric.
- ↗To a hosted notebook platform's built-in assistant: switch if you'd rather not manage a JupyterLab extension yourself.
- ↗To the underlying provider's own CLI: drop the sidebar entirely and drive Claude Code or another coding agent straight from the terminal.
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Notebook Intelligence”, and we withheld 6: 6 did not mention Notebook Intelligence. We are showing none, because we could not prove any of them are about Notebook Intelligence.
Official links
What are the best Notebook Intelligence alternatives?
The closest alternatives to Notebook Intelligence we list are ADE, Spec-Driven-Development and Ui Ux Pro Max Skill. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| ADE | Free | Free | — |
| Spec-Driven-Development | Free | Free | — |
| Ui Ux Pro Max Skill | Free | Free | — |
Alternatives to Notebook Intelligence
View all
ADE
ADE runs Claude Code, Codex, Cursor and other AI coding agents side by side in one synced agentic development environment
Spec-Driven-Development
Spec-driven development for AI coding agents: write requirements.md, design.md, and tasks.md before Claude Code, Cursor, or Copilot touch
Ui Ux Pro Max Skill
Free open-source design-intelligence skill that feeds UI styles, palettes, fonts, and chart rules into Claude Code, Cursor, and other AI coding assistants.
Tools that pair well with Notebook Intelligence
Common stack mates teams adopt alongside Notebook Intelligence, with the specific reason each pairing earns its keep.
ADE
ADE runs Claude Code, Codex, Cursor and other AI coding agents side by side in one synced agentic development environment
Spec-Driven-Development
Spec-driven development for AI coding agents: write requirements.md, design.md, and tasks.md before Claude Code, Cursor, or Copilot touch
Ui Ux Pro Max Skill
Free open-source design-intelligence skill that feeds UI styles, palettes, fonts, and chart rules into Claude Code, Cursor, and other AI coding assistants.
Notebook Intelligence vs its closest rival
Notebook Intelligence's closest head-to-head is with Geologicai.
Our Notebook Intelligence vs Geologicai verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Head-to-head comparisons
Frequently asked questions
Categories
Best-of guides
For makers of Notebook Intelligence
- Get a Verified Listing for Notebook Intelligence ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Notebook Intelligence? Help shape our editorial sentiment research.