Notebook Intelligence

Notebook Intelligence

Agentic AI coding in JupyterLab for Claude Code, Copilot, and Ollama notebooks

68/100MonitorFreeFree

If your work already lives in JupyterLab 4, NBI is the most complete agentic assistant available inside it — real Claude Code sessions, Skills, Plugins, and MCP servers, plus provider, model, and endpoint policy you can actually enforce. The free, open-source model removes the budget objection entirely. The catch is narrowness: no JupyterLab 4 means no NBI, and a light-completion user will find more configuration here than payoff.

Verified 4d ago · liveness 68/100 · cite: rightaichoice.com/tools/notebook-intelligence

Best for
  • Data scientists running agentic AI coding inside JupyterLab 4 notebooks
  • Platform teams that need 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
Not ideal for
  • 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
Visit Website

AdvancedIf you already run JupyterLab 4, you can install NBI and start a basic chat session in under 15 minutes. Configuring Claude Code or Copilot with your own API keys adds about 20 minutes. Admin policies and MCP servers require more setup, potentially 1-2 hours to fully customize. First value with simple inline chat is immediate after installation.Desktop · CLINo public APIVerified 4d ago
Pricing
Free
FreeFree tier4 hidden costs
Learning curve
Advanced
If you already run JupyterLab 4, you can install NBI and start a basic chat session in under 15 minutes. Configuring Claude Code or Copilot with your own API keys adds about 20 minutes. Admin policies and MCP servers require more setup, potentially 1-2 hours to fully customize. First value with simple inline chat is immediate after installation.
Runs on
DesktopCLI
No public API · 6 integrations
Who it's for
Data scientistML platform adminResearcher in air-gapped environment
Live sentiment
Is Notebook Intelligence actually worth it?

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
Run a free scan

3 free scans · no card needed

Skip it if

Skip Notebook Intelligence if you aren't using JupyterLab 4, want a standalone AI coding tool, or prefer a zero-config, hosted AI assistant.

The 30-second take
Biggest gripe

requires your own API keys (or local models), so you'll pay for usage plus any infrastructure.

Price reality

Notebook Intelligence is free and open source, making it attractive for cost-conscious teams already on JupyterLab. Compared to paid standalone tools like Cursor or Copilot, the savings are significant, but you bear infrastructure and configuration costs.

In short

Notebook Intelligence — Agentic AI coding in JupyterLab for Claude Code, Copilot, and Ollama notebooks. Best for Data scientists running agentic AI coding inside JupyterLab 4 notebooks, Platform teams that need enforceable provider, model, and endpoint policy on managed JupyterHub, Developers extending the assistant with custom MCP servers, Skills, and Plugins. Free to use.

What's new in Notebook Intelligence

Checked 2 days ago

Across the latest 4 updates: 4 feature updates.

What people actually say about Notebook Intelligence — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

22 mentions across 3 sources (Bluesky, GitHub, Lemmy) · researched Jul 6, 2026.

40% positive60% critical

Average across the 3 sources that answered — each source counts once, not each post.

Recurring strengths
  • +Free and open-source under GPL-3.0 license, no paywalls.
  • +First-class Claude Code agentic integration inside Jupyter notebooks.
  • +Supports multiple providers: Copilot, Ollama, OpenAI, LiteLLM, vLLM.
  • +Strong admin policy controls via environment variables.
  • +Agent mode can autonomously create, edit, and run cells.
Recurring frustrations
  • −Claude Code connectivity often fails without clear fixes.
  • −GitHub Copilot login hangs for many users.
  • −44 open issues suggest stability and polish issues.
  • −Token storage broken on VertexAI Workbenches.
  • −Setup can require significant tinkering for newcomers.
Patterns worth knowing
Broad provider support praised, but setup reliability is a problem
Seen on Bluesky, GitHub
GitHub Copilot login and authentication issues
Seen on GitHub
Claude Code agent connectivity failures
Seen on GitHub
Learning curve
advancedProductive in ~A few hours
Hidden costs people mention
  • • No hidden costs reported

Viability Score

68/100
Monitor

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

Recent activity
90
Traction
100
Site health
95
User sentiment
40
What the vendor publishes
20

Last calculated: September 2026

How we score →

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
  • First-class Claude Code integration with sessions, Skills, and Plugins
  • GitHub Copilot chat and completion support, including Codex 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
  • Admin enforcement of provider, model, and endpoint via environment variables
  • Organization-wide Skills manifest syncing
  • Security guardrails: MCP stdio-command allowlist and filesystem token-password check
  • Cell output actions: Explain, Ask, Troubleshoot

About Notebook Intelligence

FreeAdvancedNo APIDesktop · CLI

Notebook Intelligence (NBI) is an open-source JupyterLab extension that puts agentic AI coding inside your notebooks, with first-class support for Claude Code as the headline act. You get a chat sidebar that stays useful during long agent turns — tool calls render as persistent status cards with inline diffs, so you can see exactly which cell is being rewritten and why. The 5.0 release made that sidebar agent-aware, syncing open files as the agent touches them on disk, and 5.1.0 added custom spinner verbs, an MCP stdio-command allowlist, and a filesystem token-password check. Beyond Claude Code, NBI speaks to GitHub Copilot (including Codex chat models on the correct Copilot endpoint), Ollama for local models, and any OpenAI- or LiteLLM-compatible endpoint. You can drive it from the chat sidebar or inline on any cell with Cmd+I/Ctrl+I, and agent mode will autonomously create, edit, and run cells to fix its own errors. Coding-agent CLIs also launch from the JupyterLab launcher, and cell output actions give you one-click Explain, Ask, and Troubleshoot. The admin story is what separates NBI from a hobby extension. Skills, MCP Servers, and Plugins each live as top-level Settings tabs, and each carries its own force-on, force-off, or user-choice policy. Environment variables let administrators pin the provider, model, and endpoint across a managed JupyterHub deployment, and organization-wide Skills manifests can sync down to every user. It's built for people whose work already happens in a notebook — data scientists, researchers, and platform teams — rather than for developers shopping for a standalone AI editor. If your team runs JupyterLab 4 under central management and wants Claude Code behavior without leaving the browser tab, NBI is aimed squarely at you. Casual users who want zero-config completion will find the surface area larger than they need.

Behind the Verdict

Pick NBI when the notebook is the job. A research team running JupyterHub, a lab sharing analysis notebooks, anyone who resents alt-tabbing into an editor to ask an agent about the dataframe they're staring at — that's the sweet spot. The agent-aware sidebar lands well in practice: long Claude turns are normally a black box, and status cards with inline diffs turn them into something you can audit mid-run. Where it bites is the dependency. NBI is a JupyterLab 4 extension, full stop. If your org is pinned to JupyterLab 3, or your team works out of VS Code, Cursor, or a web IDE, none of this applies to you and the admin controls you're reading about are moot. There's no standalone surface to fall back on. The second caveat is configuration weight. Provider endpoints, MCP servers, Skills manifests, policy modes — for managed deployments that's the point, and the force-on/force-off/user-choice model is the right granularity for platform owners who can't personally review every tool a user wires up. For a solo analyst who just wants tab-completion, it's overhead. Compared with GitHub Copilot in a notebook or Cursor, NBI is less a code-completion tool and more an agent runtime bolted to JupyterLab. Copilot is the lighter, more universal option; Cursor is stronger if you'll leave the notebook behind. NBI wins specifically on MCP extensibility, Claude Code depth, and administrative control inside JupyterHub. In practice, model your choice on your stack. Managed JupyterHub plus a need for policy enforcement and custom tools: worth an evaluation this quarter. Air-gapped research with Ollama: also a fit, and local models keep data on-premise. Everyone else should probably wait until they're on JupyterLab 4 or pick a standalone editor. One honest note: the project ships

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.

Real-world workflow fit

Concrete scenarios for the personas Notebook Intelligence actually fits — and what changes day-one when you adopt it.

Data scientist

Debug a failing cell by opening inline chat and asking for an explanation. Agent mode fixes the code, runs it, and shows a diff.

Outcome: Resolve errors faster without switching tools, and stay confident with visible status cards.

ML platform admin

Set environment variables to enforce Claude Code as the only provider and restrict model endpoints. Deploy NBI to JupyterHub for the team.

Outcome: Ensure consistent, policy-compliant AI access across the organization without manual oversight.

Researcher in air-gapped environment

Install NBI and configure Ollama with a local model. Use the chat sidebar for code explanation and generation, entirely offline.

Outcome: Have AI assistance inside notebooks without external API dependencies.

Use Cases

Models Under the Hood

ClaudeCodexOllama

as of 2026-09-23

Limitations

  • Notebook Intelligence is an open-source JupyterLab extension (JupyterLab 4) rather than a hosted app, so it requires a local JupyterLab environment.
  • It does not ship its own models; users bring their own Claude Code, GitHub Copilot/Codex, or Ollama models, plus OpenAI/LiteLLM-compatible endpoints.
  • Features such as Skills, MCP servers, and Plugins require user configuration and may be subject to admin policy controls.

as of 2026-09-09

Verification history

We have re-verified Notebook Intelligence 9 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.

  1. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  2. — re-checked, vendor evidence unchanged
  3. — re-checked, vendor evidence unchanged
  4. — re-checked, vendor evidence unchanged
  5. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  6. — re-checked, vendor evidence unchanged

Showing the 6 most recent of 9 verification passes.

Free to cite with attribution — this page re-verifies continuously.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly
Free
Billed monthly

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Plans compared

For each published Notebook Intelligence tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.

Free

$0/mo

Ideal for

Individual data scientists and small teams already on JupyterLab 4 who need an AI assistant without extra cost and are comfortable managing their own API keys.

What this tier adds

This is the only tier—it's open-source and free. All current features including Claude Code integration, agent mode, MCP management, and admin policies are available at no charge.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • requires your own API keys (or local models), so you'll pay for usage plus any infrastructure.
  • JupyterLab 4 only—teams on older versions must upgrade, which may involve migration effort.
  • Advanced features like MCP servers and Skills require configuration, adding setup time.
  • No hosted option; you need to manage your own environment and updates.

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.

Notebook Intelligence is free and open source, making it attractive for cost-conscious teams already on JupyterLab. Compared to paid standalone tools like Cursor or Copilot, the savings are significant, but you bear infrastructure and configuration costs.

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.

If you already run JupyterLab 4, you can install NBI and start a basic chat session in under 15 minutes. Configuring Claude Code or Copilot with your own API keys adds about 20 minutes. Admin policies and MCP servers require more setup, potentially 1-2 hours to fully customize. First value with simple inline chat is immediate after installation.

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.

Migrating in
  • →From JupyterLab 3: Upgrade to JupyterLab 4 first, then install Notebook Intelligence as a standard extension.
Migrating out
  • ↗To Cursor: Export your notebook files and open them in Cursor, where you'll have AI features out of the box without JupyterLab.

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.

Tools that pair well with Notebook Intelligence

Common stack mates teams adopt alongside Notebook Intelligence, with the specific reason each pairing earns its keep.

Featured Head-to-Head Comparisons

Alternatives to Notebook Intelligence

View all
Claude Code

Claude Code

Claude Code is Anthropic's agentic coding assistant that plans, edits, and runs commands across your repo from the terminal, IDE, or browser.

FreemiumTry
GitHub Copilot

GitHub Copilot

GitHub Copilot is an AI coding agent that completes code, reviews pull requests, and runs agents from issue to merge

FreemiumTry
Claude

Claude

Claude is Anthropic's AI assistant for long-document analysis, coding, and agentic work in chat and Cowork.

FreemiumTry

Frequently Asked Questions

Used Notebook Intelligence? Help shape our editorial sentiment research.