datalayer
jupyter-server-nbmodel
Python

🪐 Jupyter Server NbModel - Keep your sessions by executing code from a server-side NbModel.

Last updated Apr 30, 2026
41
Stars
13
Forks
24
Issues
0
Stars/day
Attention Score
57
Language breakdown
Python 74.6%
TypeScript 21.5%
JavaScript 1.9%
Makefile 1.6%
CSS 0.4%
Files click to expand
README

Datalayer

Become a Sponsor

🪐 Jupyter Server NbModel

Github Actions Status Binder

Stop session timeouts and lost.

A Jupyter Server extension to execute code from the server-side NbModel.

Jupyter Server NbModel Demo
Side-by-side comparison: Without jupyterservernbmodel (left), notebook execution stops when reloading the page; with jupyterservernbmodel (right), execution continues uninterrupted even after reload.

This extension is composed of a Python package named jupyterservernbmodel for the server extension and a NPM package named @datalayer/jupyter-server-nbmodel for the frontend extension.

Requirements

  • Jupyter Server
  • \[RECOMMENDED\] Real-time collaboration for JupyterLab/Notebook:
This will push the kernels results in the notebook from the server.

Install

To install the extension for use in JupyterLab or Notebook 7, execute:

pip install "jupyterservernbmodel[lab]"

For API-only use:

pip install jupyterservernbmodel

Uninstall

To remove the extension, execute:

pip uninstall jupyterservernbmodel

Troubleshoot

If you are seeing the frontend extension, but it is not working, check that the server extension is enabled:

jupyter server extension list

If the server extension is installed and enabled, but you are not seeing the frontend extension, check the frontend extension is installed:

jupyter labextension list

How does it works

Generic case

Execution of a Python code snippet: print("hello")

sequenceDiagram
    actor Frontend; participant Shared Document; actor Server; participant ExecutionStack; actor Kernel
    Frontend->>Shared Document: [*] busy
    Frontend->>+Server: POST /api/kernels/<id>/execute
    Server->>+ExecutionStack: put() request into queue
    ExecutionStack->>Kernel: Execute request msg
    activate Kernel
    ExecutionStack-->>Server: Task uid
    Server-->>-Frontend: Returns task uid
    loop Running
        Kernel->>Server: stream / displaydata / executeresult / error msg
        Server->>Shared Document: Add output
        Shared Document->>Frontend: Document update
    end
    loop While status is 202
        Frontend->>+Server: GET /api/kernels/<id>/requests/<uid>
        Server->>ExecutionStack: get() task result
        ExecutionStack-->>Server: null
        Server-->>-Frontend: Request status 202
    end
    Kernel-->>Server: Execution reply
    Server->>Shared Document: [𝒏] idle
    Server-->>ExecutionStack: execution_count, status, outputs
    Shared Document->>Frontend: [𝒏] idle
    deactivate Kernel
    Frontend->>+Server: GET /api/kernels/<id>/requests/<uid>
    Server->>ExecutionStack: get() task result
    ExecutionStack-->>Server: execution_count, status, outputs
    Server-->>-Frontend: Status 200 & { execution_count, status, outputs }

With input case

Execution of a Python code snippet: input("Age:")

sequenceDiagram
    actor Frontend; participant Shared Document; actor Server; participant ExecutionStack; actor Kernel
    Frontend->>Shared Document: [*] busy
    Frontend->>+Server: POST /api/kernels/<id>/execute
    Server->>+ExecutionStack: put() request into queue
    ExecutionStack->>Kernel: Execute request msg
    activate Kernel
    ExecutionStack-->>Server: Task uid
    Server-->>-Frontend: Returns task uid
    loop Running
        Kernel->>Server: stream / displaydata / executeresult / error msg
        Server->>Shared Document: Add output
        Shared Document->>Frontend: Document update
    end
    loop While status is 202
        Frontend->>+Server: GET /api/kernels/<id>/requests/<uid>
        Server->>ExecutionStack: get() task result
        ExecutionStack-->>Server: null
        Server-->>-Frontend: Request status 202
    end
    Kernel->>ExecutionStack: Set pending input
    Frontend->>+Server: GET /api/kernels/<id>/requests/<uid>
    Server->>ExecutionStack: get() task result
    ExecutionStack-->>Server: Pending input
    Server-->>-Frontend: Status 300 & Pending input
    Frontend->>+Server: POST /api/kernels/<id>/input
    Server->>Kernel: Send input msg
    Server-->>-Frontend: Returns
    loop While status is 202
        Frontend->>+Server: GET /api/kernels/<id>/requests/<uid>
        Server->>ExecutionStack: get() task result
        ExecutionStack-->>Server: null
        Server-->>-Frontend: Request status 202
    end
    Kernel-->>Server: Execution reply
    Server->>Shared Document: [𝒏] idle
    Server-->>ExecutionStack: execution_count, status, outputs
    Shared Document->>Frontend: [𝒏] idle
    deactivate Kernel
    Frontend->>+Server: GET /api/kernels/<id>/requests/<uid>
    Server->>ExecutionStack: get() task result
    ExecutionStack-->>Server: execution_count, status, outputs
    Server-->>-Frontend: Status 200 & { execution_count, status, outputs }
\[!NOTE\]
The code snippet is always send in the body of the POST /api/kernels/<id>/execute
request to avoid document model discrepancy; the document on the backend is only
eventually identical with the frontends (document updates are not instantaneous).
>
The ExecutionStack maintains an execution queue per kernels to ensure execution
order.

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment

Change directory to the jupyterservernbmodel directory

Install package in development mode

pip install -e ".[test]"

Link your development version of the extension with JupyterLab

jupyter labextension develop . --overwrite

Server extension must be manually installed in develop mode

jupyter server extension enable jupyterservernbmodel

Rebuild extension Typescript source after making changes

jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch

Run JupyterLab in another terminal

jupyter lab --autoreload

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

# Server extension must be manually disabled in develop mode
jupyter server extension disable jupyterservernbmodel
pip uninstall jupyterservernbmodel

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named jupyter-server-nbmodel within that folder.

Testing the extension

Server tests

This extension is using Pytest for Python code testing.

Install test dependencies (needed only once):

pip install -e ".[test]"

Each time you install the Python package, you need to restore the front-end extension link

jupyter labextension develop . --overwrite

To execute them, run:

pytest

Frontend tests

This extension is using Jest for JavaScript code testing.

To execute them, execute:

jlpm
jlpm test

Integration tests

This extension uses Playwright for the integration tests (aka user level tests). More precisely, the JupyterLab helper Galata is used to handle testing the extension in JupyterLab.

More information are provided within the ui-tests README.

Manual testing

# Terminal 1.

You can also invoke make jupyter-server

jupyter server --port 8888 --autoreload --ServerApp.disablecheckxsrf=True --IdentityProvider.token= --ServerApp.port_retries=0
# Terminal 2.
KERNEL=$(curl -X POST http://localhost:8888/api/kernels)
echo $KERNEL

KERNEL_ID=$(echo $KERNEL | jq --raw-output '.id') echo $KERNEL_ID

RESPONSE=$(curl --include http://localhost:8888/api/kernels/$KERNEL_ID/execute -d "{ \"code\": \"print('1+1')\" }") echo $RESPONSE

RESULT_PATH=$(echo $RESPONSE | grep -oP 'Location:\s*\K[^ ]+' | tr -d '\r\n') echo $RESULT_PATH

URL="http://localhost:8888${RESULT_PATH}" echo $URL

curl "$URL"

{"status": "ok", "executioncount": 1, "outputs": "[{\"outputtype\": \"stream\", \"name\": \"stdout\", \"text\": \"1+1\\n\"}]"}

Running Tests

Install dependencies:

pip install -e ".[test]"

To run the python tests, use:

pytest

To test a specific file

pytest jupyterservernbmodel/tests/test_handlers.py

To run a specific test

pytest jupyterservernbmodel/tests/testhandlers.py -k "testpost_execute"

Development uninstall

pip uninstall jupyterservernbmodel

Packaging the extension

See RELEASE

🔗 More in this category

© 2026 GitRepoTrend · datalayer/jupyter-server-nbmodel · Updated daily from GitHub