Jupyter | 2i2c

Report from the Jupyter and AI community meetup

Thu, 23 Apr 2026 00:00:00 +0000

A small group of Jupyter community members recently met in Seattle to demo Jupyter workflows augmented with AI tools and discuss what’s next. This is a quick report-out about what stood out.

The conversations focused on what agentic workflows could unlock for researchers and students - with broad acknowledgement that deployment, security, authorization, and ethics still have a lot to be worked out.

Here are a few highlights from the demos.

Jupyter AI and the Agent Client Protocol #

Jupyter AI v3 is adding support for the Agent Client Protocol (ACP), enabling multi-agent collaboration within JupyterLab. We saw how a single request could be split across multiple specialized agents based on each one’s skills, similar to this demo from JupyterCon 2025.

Some things still to figure out:

No tool isolation yet - agents aren’t scoped by user role or security group.
Manual configuration required - agents running locally need to be registered by hand.
A future goal is for JupyterLab to auto-detect locally installed agents, or for LLM providers to contribute integrations directly.

The Jupyter AI team also shared a new “Personas” abstraction that lets you define a skill-specific agent in just a few lines of Python. Personas open the door to domain-specific agents or agents with crafted “personalities”. They are written in a few lines of Python, though we discussed the possibility of using markdown instead. This seems to be evolving rapidly!

Jupyter AI v3.0.0 has since been released.

Notebook CLI #

nb-cli is a Rust-based tool for interacting with notebooks from the command line - changing cells, running them, checking errors, and rendering the notebook in the console. It can also connect to remote JupyterLab instances, making it useful for headless workflows like CI pipelines or batch grading.

Sidebar comments and Real-time collaboration #

A demo showed Google Docs-style side-panel comments for .ipynb files. Previous collaboration efforts used Conflict-free Replicated Data Types (CRDTs) for multi-cursor editing, but the team felt that approach may not have hit the mark. Side-panel comments felt more natural, though how this extends to .py files is still an open question.

Opportunities for 2i2c #

The meeting helped us understand the role we could play in this space. We think there’s opportunity to help facilitate the use of agents on shared infrastructure, particularly around the upstream control planes for deployment, administration, and authorization. We can also help facilitate community conversations about the ethics and impact of AI tools on open science.

Acknowledgements #

The Jupyter Foundation for supporting the event.
Zach Sailer (Apple), for organizing this meetup.
Chris Holdgraf for editing and adapting the original content for this post.

Report from the Jupyter Security Working Group security tooling sprint

Wed, 08 Apr 2026 00:00:00 +0000

The Jupyter Security Working Group recently held a Security Tooling Sprint. It was a timely event given the recent spate of software supply chain attacks across the tech world.

The sprint covered two main areas:

Governance and strategy — conversations about responsibility and accountability in the face of AI, with emphasis on ensuring humans are ultimately responsible for code committed to Jupyter subprojects. The group also discussed how security could benefit from working group members regularly attending subproject meetings like the JupyterHub Collaboration Cafes.
Automation and tools — the group evaluated several tools for improving security posture across the Jupyter ecosystem. Here are a few that stood out:
- Semgrep as an alternative vulnerability scanner to CodeQL
- Grype, Checkov, and Kubescape for cloud infrastructure misconfiguration checks
- Schemathesis and restler-fuzzer for API fuzz testing

One challenge we discussed was how blindly running security scanning tools generates many false positives. There’s real effort needed to tune these tools for each project’s edge cases before they’re useful in automation. On a related note, we discussed the increase in AI-generated (or AI-assisted) vulnerability and security reports, and the challenges associated with sifting through all of those pieces of information.

Acknowledgements #

Thanks to the jupyter security working group for providing leadership and organizing, in particular Joe Lucas!
Thanks to the Jupyter Foundation for funding community meetings like these.

April joins the Jupyter Community Building Working Group

Fri, 23 Jan 2026 00:00:00 +0000

We’re pleased to share that our People Operations Lead, April Johnson, has joined the Jupyter Community Building Working Group!

This kind of work reflects how we think about foundational contributions and upstream support: strengthening the social infrastructure that helps open source communities grow and thrive, not just contributing code and running infrastructure. April brings deep experience building teams and communities, and we’re proud to support her upstream efforts in this way.

Acknowledgements #

Thanks to the Jupyter Community Building Working Group for their leadership in building a stronger Jupyter community, and for welcoming April

2i2c at JupyterCon 2025: Helping communities navigate the Interactive Computing ecosystem

Thu, 20 Nov 2025 00:00:00 +0000

This year several team members attended JupyterCon 2025 to show off our own work and the upstream work that we’ve been doing in open source. JupyterCon recently shared the videos of all talks, so here’s a quick run-down of 2i2c’s contributions and where you can watch more.

Building computational narratives with Jupyter Book #

Introducing Jupyter Book 2: Next-generation Tools for Creating Computational Narratives - Chris Holdgraf and Rowan Cockett ( Curvenote) introduce the next generation of Jupyter Book, built on modern tooling and designed for creating rich computational narratives.

Tutorial: Build-a-Jupyter Book With the Turing Way - Angus Hollands co-led this hands-on tutorial teaching participants how to create their own Jupyter Books using examples from the Turing Way.

JupyterHub’s evolution and sustainable operations #

Not Just for Notebooks: JupyterHub in 2025 - Yuvi Panda explores how JupyterHub is evolving beyond just notebooks to support a wider range of interactive computing workflows.

Cloudy With a Chance of Savings: Per-User Usage and Cost Monitoring for JupyterHubs in the Cloud - Jenny Wong presents our recent work improving tools and approaches for monitoring per-user cloud costs in JupyterHub deployments, helping communities operate more sustainably.

Lightning Talk: Controlling Home Directory Costs (with User Empathy) on the Cloud - Yuvi Panda shares practical strategies for managing home directory storage costs while keeping user experience in mind, using jupyterhub-home-nfs.

Finally, there were also several talks that weren’t by 2i2c team members, but were partially enabled by 2i2c’s collaboration. We’re particularly proud of these, because it’s an example of us bringing others into the ecosystem and empowering them to contribute.

Understanding the JupyterHub community #

Findings from the Voices of JupyterHub report - This community strategy talk shares insights from conversations with JupyterHub users and operators about their needs and challenges. It’s not given by a 2i2c team member, but many of us have been involved in guiding (and being participants in!) this project.

MyST-ifying Project Pythia - Julia Kent of NSF NCAR discusses Project Pythia, an open-source platform dedicated to educating geoscientists on Python for complex Earth data analysis. Learn how Project Pythia manages its expansive repository of “cookbooks” and educational content, detailing their strategic shift to MyST Markdown and Jupyter Book 2 to drastically improve project sustainability and reduce maintenance overhead.

How CryoCloud built a healthy open science community #

Building a successful open science community in the cloud - Tasha Snow shares key insights from running the CryoCloud JupyterHub, emphasizing that a successful scientific community relies on both technology and social innovation. She shares data-driven results on how shared JupyterHubs can significantly reduce research computing costs and accelerate scientific iteration. She also explores the critical balance between platform capabilities and the need for social infrastructure to overcome technical barriers and foster true collaboration.

Updates from Chris' position on the Jupyter Executive Council and Foundation Board

Tue, 23 Sep 2025 00:00:00 +0000

This is a running blog post for Chris to share out community updates from his time on the Jupyter Executive Council. See context for this page.

Updates for the Jupyter community from Chris #

Chris aims to write monthly updates for Jupyter’s community in the Jupyter Community Forum to share his perspective on what the council is up to. We’ll update this index post as new posts are available.

Blog posts about Chris’ experience on the executive council #

Chris blogs now and then to share his thoughts, important announcements, and provide major updates from his perspective on the executive council. Here are the posts that have come out of this effort.

Your Ideas, Our Support: Jupyter Community Call For Funding Proposals
Why open source foundations try to fund systems, not development - May 31, 2025
Jupyter can align the needs of its community and its foundation by enabling contribution - Mar 22, 2025
The relationship between the Jupyter Executive Council, Software Steering Council, and Foundation - Mar 02, 2025
Ways the Jupyter Foundation could support open source projects - Feb 26, 2025
Running for the Jupyter Executive Council - Jan 14, 2025

2i2c’s commitment to supporting open source communities #

In early 2025, Chris was elected to the Jupyter Executive Council. We’re tracking these efforts because providing leadership and community support to open source projects is a key Foundational contribution we wish to make for open source projects. 2i2c makes time for team members to contribute upstream in strategic ways like this as part of our commitment to open practices. However, this kind of work is very difficult to track! This blog post is an attempt at putting these efforts into one place for us to track and for others to discover.

Acknowledgements #

2i2c’s member communities support Foundation open source contributions like this with their membership fees.
The Navigation Fund provides strategic funding support for 2i2c which covers major open source leadership contributions like this.

2i2c's submissions to JupyterCon 2025

Sat, 19 Jul 2025 00:00:00 +0000

Update: The talks are now live! See this blog post with links to our videos.

We were excited to hear that JupyterCon is happening again in 2025. The Call for Proposals just wrapped up, and our team was involved in preparing and submitting several directly from 2i2c as well as from the ecosystem in general.

Enjoy brief summaries of the proposals we contributed to below. Let us know if you have ideas for future talks you want to hear from us?

Note: Many of these submissions were written in collaboration with others in the open-source projects we participate in. Particularly, in JupyterHub and JupyterBook.

JupyterHub: A multi-user server for Jupyter notebooks #

This is how JupyterHub was described when it was announced in 2015, 10 years ago. The focus was on bringing Jupyter Notebooks to multiple users on shared infrastructure. The Jupyter Notebooks focus was so strong that Jupyter was even in the name of the project! Fast forward 10 years, & this is still the most common perception of JupyterHub.

However, this has not been true for a long time now. Instead of setting up 5 different kinds of infrastructure to support your users based on what kind of interface they like to use ( JupyterLab, RStudio, Linux Desktop tools like QGIS or Napari, Visual Studio Code, full ssh (!?), etc) for their interactive computing, you can set up a JupyterHub that supports all of those! Meet your users where they are, rather than force them to conform to using only a specific set of tools.

Come to this talk to:

See cool demos of various popular applications running on JupyterHub seamlessly
Understand the security model of JupyterHub & how that enables these cool demos
Learn how you can set up your own application to run in JupyterHub
Influence the future of how JupyterHub is marketed

Cloudy with a Chance of Savings: Per-User Usage and Cost Monitoring for JupyterHubs in the Cloud #

Cloud cost monitoring is moving beyond just preventing runaway cost explosions – it’s about empowering JupyterHub administrators with the guardrails they need to run efficient, transparent, and sustainable infrastructures. A cloud cost bill can show a broad view of services and machines provisioned, but how can we provide granular insights into each user and the value they are deriving from the hub on an application level?

We’ve developed several open-source components towards answering this question:

Metric Collection – Prometheus collects resource usage metrics (including CPU, memory, and storage) from individual user pods via standard and custom exporters.
Cost Estimation – Usage is correlated with AWS cost data to estimate per-user costs.
Visualization – Grafana dashboards display rich, interactive views of usage and cost data, making it easy to monitor trends, identify high-cost workloads, and generate reports for funders and decision-makers.

This approach delivers cloud observability and cost transparency that can be reliably deployed using Kubernetes and integrated with Zero to JupyterHub distributions.

Controlling home directory costs (with user empathy) on the cloud with jupyterhub-home-nfs #

User home directories on JupyterHubs deployed in cloud providers has been a pain point for both end users and administrators. Administrators feel the pain of cloud costs for home directory storage (sometimes higher than compute!). No user wants to receive an email saying “well, this code you copy pasted downloaded 3TB of netcdf files into your home directory, and now we have used up our entire team’s cloud budget for the next 2 years” (true story).

The jupyterhub-home-nfs open source project is a JupyterHub native, cloud agnostic solution to these problems. Administrators can do per user limits, tune performance, report on usage and make cloud cost conscious choices around overprovisioning. It provides users empathetic guardrails to prevent them from overuse, rather than punitive gates that zap them after the fact.

In this short talk, we will:

Describe the core of the problem, and how it manifests for users and admins.
Review current solutions and their limitations
Introduce jupyterhub-home-nfs and how it moves the solution space forward
Demo how this looks like for an end user
Talk about future direction, and opportunities for collaboration

Rebuilding user trust in `mybinder.org` #

Have you clicked a mybinder.org link, waited for it to start and gave up after it took far too long to start? Or just failed?

Have you stopped using mybinder.org for your tutorials, repositories and presentations because you could no longer rely on it to work each time?

mybinder.org is open infrastructure run by incredible volunteers (who go above and beyond constantly) in the Jupyter community. Is ‘slow fade into unreliability’ just the fate of all openly run infrastructure?

But perhaps maybe, just maybe, you have tried doing that again recently, & noticed improvements! Launches are more reliable. Faster. The UI looks better. Maybe things are getting better?

This talk will go through the problems facing mybinder.org & what we are doing about it. Come to this talk to find out:

How is mybinder.org run?
What are the structural issues facing open infrastructure services like mybinder.org?
What sustainability experiments are we running to improve reliability and rebuild user trust?
Has reliability actually improved?
How can I help?

Can your JupyterHub handle your workload? Performance testing with `jupyterhub-simulator` #

Your JupyterHub is all set up, and you’re excited to use it for your workshop of 60 students. Or your class of 600 students. Or your research group of 5 people with complex workflows.

You feel your infrastructure should hold up fine, but do you know if your infrastructure will hold up fine? Is that just excitement, or is there a little bit of nervousness in there too? Wouldn’t it be nice to test and know for sure?

jupyterhub-simulator is an open source project that allows you to describe what you expect your users to be doing - starting servers, clicking on nbgitpuller links, running notebooks, etc. Once you have described it, you can then simulate any number of users doing that workflow simultaneously, and verify that your JupyterHub can handle that workload. If it can’t, tweak your infrastructure and try again until it does!

In this talk you will learn:

What is jupyterhub-simulator?
How can I describe my expected workflow?
How can I test if N users can do this workflow all simultaneously?
How can I visualize the performance of my infrastructure so I can tweak its configuration and try the simulation again?

Not just for notebooks: JupyterHub in 2025 #

JupyterHub: A multi-user server for Jupyter notebooks

Come to this talk to:

See cool demos of various popular applications running on JupyterHub seamlessly
Understand the security model of JupyterHub & how that enables these cool demos
Learn how you can set up your own application to run in JupyterHub
Influence the future of how JupyterHub is marketed

Introducing Jupyter Book 2.0 #

This is a community talk from the Jupyter Book team, detailing the principles behind the new MyST Document Engine and Jupyter Book 2’s upcoming release. We’ll share the text when the Jupyter Book team posts it publicly.

You don’t need to contribute more to open source, you need to go to therapy #

Open source communities can be incredible and irreplaceable sources of human connection in our lives, offering a unique kind of fulfillment hard to find elsewhere. This feeling of fulfillment and approval can, for some people, be a soothing balm in an otherwise rough life. However, it has the be part of a healthy, balanced ecosystem of different kinds of connections offering different kinds of fulfillment . If a significant chunk of fulfillment in your life comes from the open source work you do, unbalanced by other sources, that can quickly become unhealthy for both you and the community. Disagreements are more likely to become high stakes. Interactions can quickly become emotionally charged and filled with hard to interpret subtext. This can both burn you out, and drive away potential new community members.

This talk explores the why emotional regulation is a critical skill for participating in open source communities, and how therapy can be a tool for learning that skill. Come to learn:

What is emotional regulation?
Why should I care?
What is therapy and how can I access it?
Wait that’s not what I thought therapy was! Are you telling me Missy Armitage lied in Get Out?!
What negative effects do communities feel?

What 2i2c has learned while trying to build sustainable relationships with Jupyter’s community. #

2i2c is a non-profit organization that fosters co-creation and collaboration between science communities and open source communities. We are deeply embedded in an international network of research and education communities, as well as open source communities that underlie their infrastructure (particularly in the Jupyter ecosystem). Our technical infrastructure is built entirely with open source components that we contribute to, but do not control. This is a really hard problem to solve!

We’ve learned a lot in the first four years of our existence. This talk will describe how our organization approaches a healthy and productive open source relationship with the Jupyter (and broader scientific python) ecosystem. It’ll cover some of the major mistakes we’ve made, lessons learned, and where we think we’ve had impact. We aim to make this talk full of practical learnings that others can follow in building sustainable open science organizations that contribute to a healthy and vibrant open source ecosystem. Our goal will be to provide inspiration to others that are interested in building on top of open source projects like Jupyter, and want to do so in a way that is healthy and sustainable.

Chris is joining Project Jupyter's Executive Council

Mon, 10 Mar 2025 00:00:00 +0000

We are proud to announce that 2i2c’s Executive Director, Chris Holdgraf, was recently elected to Jupyter’s Executive Council. The 2i2c team discussed whether Chris should run for this position last year, and concluded that it was a way for our non-profit to both support Jupyter’s mission at a strategic level, and represent the interests of research and education communities in Jupyter’s direction. Chris wrote a blog post about his reasons for running with more information.

One of Chris’ goals is to be a transparent source of information about what the council is working on, where its priorities lie, and what are the major challenges it is trying to tackle. He’s written two blog posts that describe some of his experiences so far, at the links below:

We’re hopeful that this is a way for 2i2c to scale its impact and lean into its commitment to open technology. Chris intends to keep writing about his personal experience via his blog, and we’ll provide updates here for major developments that are relevant to 2i2c’s network of communities. We’re proud to have Chris in this role, and excited for his contributions to the Jupyter community!

Acknowledgements #

Strategic open source support like this is supported by a grant from The Navigation Fund and fees from our member organizations.

Jupyter | 2i2c

Report from the Jupyter and AI community meetup

Jupyter AI and the Agent Client Protocol #

Notebook CLI #

Sidebar comments and Real-time collaboration #

Opportunities for 2i2c #

Acknowledgements #

Report from the Jupyter Security Working Group security tooling sprint

Acknowledgements #

April joins the Jupyter Community Building Working Group

Acknowledgements #

2i2c at JupyterCon 2025: Helping communities navigate the Interactive Computing ecosystem

Building computational narratives with Jupyter Book #

JupyterHub’s evolution and sustainable operations #

Understanding the JupyterHub community #

Pythia sharing their MyST journey #

How CryoCloud built a healthy open science community #

Updates from Chris' position on the Jupyter Executive Council and Foundation Board

Updates for the Jupyter community from Chris #

Blog posts about Chris’ experience on the executive council #

2i2c’s commitment to supporting open source communities #

Acknowledgements #

2i2c's submissions to JupyterCon 2025

JupyterHub: A multi-user server for Jupyter notebooks #

Cloudy with a Chance of Savings: Per-User Usage and Cost Monitoring for JupyterHubs in the Cloud #

Controlling home directory costs (with user empathy) on the cloud with jupyterhub-home-nfs #

Rebuilding user trust in mybinder.org #

Can your JupyterHub handle your workload? Performance testing with jupyterhub-simulator #

Not just for notebooks: JupyterHub in 2025 #

Introducing Jupyter Book 2.0 #

You don’t need to contribute more to open source, you need to go to therapy #

What 2i2c has learned while trying to build sustainable relationships with Jupyter’s community. #

Chris is joining Project Jupyter's Executive Council

Acknowledgements #

Rebuilding user trust in `mybinder.org` #

Can your JupyterHub handle your workload? Performance testing with `jupyterhub-simulator` #