Status: In Progress · Proposal
August 2026¶
Summary of Work Completed¶
The Plugin Playground work is nearly complete, with only one deliverable stretch-goal (LSP integration for lite deployment) remaining.
Deliverables/Milestones¶
The stretch-goal LSP integration for JupyterLite deployment is in progress, awaiting release of the dependencies:
WIP PoC/working stage jupyterlab
/plugin -playground #225 Released: LSP connection deduplication jupyterlab
/jupyterlab #18980 In pre-release: runtime LSP provider registration jupyterlab
/jupyterlab #18985 In pre-release: startup extensions for JavaScript kernels jupyterlite
/javascript -kernel #29
Metrics: The JupyterLite-based deployment recorded 118 unique visitors (this excludes anyone with an ad blocker enabled).
We track most of the issues and pull requests associated with this proposal in this public GitHub project.
Challenges or Risks¶
We exhausted the budget with the stretch-goal not fully resolved (it works, but is not merged yet). We will aim to complete this anyway.
Budget Update¶
As of 25th August 2026 we used 18,270 USD out of 18,270 USD budget.
Next Steps¶
We will strive to complete the lite-LSP integration as the releases propagate the foundational work.
June 2026¶
Summary of Work Completed¶
The Plugin Playground work is nearly complete, with only one deliverable stretch-goal (LSP integration for lite deployment) remaining.
Deliverables/Milestones¶
The version 1.0.0 was released (https://
github .com /jupyterlab /plugin -playground /releases /tag /v1 .0.0) Following notable improvements were implemented:
Add currently loaded playground plugins panel (jupyterlab
/plugin -playground #245) Add “Ask AI” action for JS log errors (jupyterlab
/plugin -playground #231) Resolve shared runtime modules (jupyterlab
/plugin -playground #219) We hardened the Binder deployment (jupyterlab
/plugin -playground #237)
The stretch-goal LSP integration for JupyterLite deployment is in-progress:
WIP PoC/working stage jupyterlab
/plugin -playground #225 Merged: LSP connection deduplication jupyterlab
/jupyterlab #18980 In review: runtime LSP provider registration jupyterlab
/jupyterlab #18985 In review: startup extensions for JavaScript kernels jupyterlite
/javascript -kernel #29
Multiple bugs were fixed based on the testing/feedback:
Fix launcher SVG import (jupyterlab
/plugin -playground #218) Update minimum required version of jupyterlab-open-url-parameter (jupyterlab
/plugin -playground #220) Fix server extension loading when package.json is missing (jupyterlab
/plugin -playground #224) Fix dynamic settings reload consistency (jupyterlab
/plugin -playground #223) Improve Plugin Playground authoring guidance for multi-file plugins (jupyterlab
/plugin -playground #242) Include notebook files in Share Package selection (jupyterlab
/plugin -playground #241)
We improved testing:
Replace Node example check with Playwright test (jupyterlab
/plugin -playground #213) Add dynamic settings rollback restore test (jupyterlab
/plugin -playground #227)
We spread the word:
presentation during jupyter-ai workshop in London
Metrics: The JupyterLite-based deployment recorded 71 unique visitors (this excludes anyone with an adblock enabled) from 20 countries.
We track most of the issues and pull requests associated with this proposal in this public GitHub project.
Challenges or Risks¶
None.
Budget Update¶
As of 23rd June 2026 we used 17,671.80 USD out of 18,270 USD budget.
Next Steps¶
This work is nearly complete. We will strive to complete the lite-LSP integration (stretch goal) within the remaining budget.
April 2026¶
Summary of Work Completed¶
The baseline Plugin Playground work is complete, with only one deliverable (LSP integration) remaining, and the work tracking the projected budget.
We track some of the issues and pull requests associated with this proposal in this public GitHub project.
Deliverables/Milestones¶
The
plugin-playgroundextension was upgraded to support JupyterLab 4 and Notebook 7.The binder deployment was fixed.
Following major improvements were implemented:
Show list of available tokens in the sidebar panel (jupyterlab
/plugin -playground #27) Integrate with jupyterlab/extension-examples (jupyterlab
/plugin -playground #25) Allowing exploring docs, source links for core (and extension) modules (jupyterlab
/plugin -playground #49) Integration into documentation (jupyterlab
/jupyterlab #18726) Share link functionality (jupyterlab
/plugin -playground #118) AI integration/enablement (jupyterlab
/plugin -playground #78)
Dissemination: we presented the work on multiple Jupyter contributor meetings, and shared it via Jupyter Forum (https://
discourse .jupyter .org /t /plugin -playground -create -your -jupyter -extension -first -1 -0 -pre -release) Collecting impact metrics: we integrated plausible and began recording metrics from RDT/GitHub (jupyterlab
/plugin -playground #148) The v1.0 alpha and beta versions were released (jupyterlab
/plugin -playground #163)
Challenges or Risks¶
None.
Budget Update¶
As of 26th April 2026 we used 13,579 USD out of 18,270 USD budget.
Next Steps¶
We plan to complete the last deliverable (stretch goal), the lite-LSP integration next, that would surface the linting errors and other coding assistance features in the LSP deployment.
We would also like to improve the AI integration by exposing the LSP awareness via commands to the AI agent.
We will continue to:
seek feedback from the community, disseminating and sharing the progress on blog.jupyter.org and presenting during the community meetings
fix any issues reported by the community
February 2026¶
Summary of Work Completed¶
No work has been completed yet. We allocated time to commence work in early March 2026.
We track some of the issues and pull requests associated with this proposal in this public GitHub project.
Deliverables/Milestones¶
NA
Challenges or Risks¶
None.
Budget Update¶
As of 20th Feb 2026 we used 0 USD out of 18,270 USD budget.
Next Steps¶
We plan to begin with upgrading the plugin-playground to support JupyterLab 4 and Notebook 7 and fixing the binder deployment.