jupyterlab_notifications_extension
v1.1.26
Published
Jupyterlab extension to receive and display notifications in the main panel. Those can be from the jupyterjub administrator or from other places.
Maintainers
Readme
jupyterlab_notifications_extension
JupyterLab extension for sending notifications using the native JupyterLab notification system. External systems and extensions send alerts and status updates that appear in JupyterLab's notification center.
This extension serves as the notification backbone for Stellars JupyterHub Platform for Data Science, allowing administrators to broadcast notification messages to all running JupyterLab servers.
Five notification types with distinct visual styling provide clear status communication:

Access via command palette for quick manual notification sending:

Interactive dialog with message input, type selection, auto-close timing, and action button options:

Key Features:
- REST API for external systems to POST notifications with authentication
- Command palette integration with interactive dialog
- Programmatic command API for extensions and automation
- Five notification types (info, success, warning, error, in-progress)
- Configurable auto-close with millisecond precision or manual dismiss
- Optional action buttons (currently dismiss only)
- Broadcast delivery via 30-second polling
- In-memory queue cleared after delivery
Installation
pip install jupyterlab_notifications_extensionRequirements: JupyterLab >= 4.0.0
API Reference
POST /jupyterlab-notifications-extension/ingest
Send notifications to JupyterLab. Requires authentication via Authorization: token <TOKEN> header or ?token=<TOKEN> query parameter. Requests from localhost (127.0.0.1, ::1) skip authentication.
Endpoint: POST /jupyterlab-notifications-extension/ingest
Request Body (application/json):
{
"message": "Your notification message",
"type": "info",
"autoClose": 5000,
"actions": [
{
"label": "Click here",
"caption": "Additional info",
"displayType": "accent"
}
]
}Request Parameters:
| Field | Type | Required | Default | Description |
| ----------- | -------------- | -------- | -------- | ----------------------------------------------------------------------------------------------------------------------- |
| message | string | Yes | - | Notification text (max 140 characters) |
| type | string | No | "info" | Visual style: default, info, success, warning, error, in-progress |
| autoClose | number/boolean | No | 5000 | Milliseconds before auto-dismiss. false = manual dismiss only. 0 = silent mode (notification center only, no toast) |
| actions | array | No | [] | Action buttons (see below) |
Action Button Schema:
| Field | Type | Required | Default | Description |
| ------------- | ------ | -------- | ----------- | ------------------------------------------------- |
| label | string | Yes | - | Button text |
| caption | string | No | "" | Tooltip text |
| displayType | string | No | "default" | Visual style: default, accent, warn, link |
Note: Action buttons are purely visual. Clicking any button dismisses the notification using JupyterLab's native behavior. Buttons do not trigger custom callbacks or actions.
Response (200 OK):
{
"success": true,
"notification_id": "notif_1762549476180_0"
}Error Responses:
400 Bad Request- Missingmessagefield or invalid JSON401 Unauthorized- Missing or invalid authentication token500 Internal Server Error- Server-side processing error
Usage Examples
From JupyterLab Extensions
Send notifications programmatically from other extensions:
// Basic notification
await app.commands.execute('jupyterlab-notifications:send', {
message: 'Operation complete'
});
// Custom type and auto-close
await app.commands.execute('jupyterlab-notifications:send', {
message: 'Build finished successfully',
type: 'success',
autoClose: 3000
});
// With action button
await app.commands.execute('jupyterlab-notifications:send', {
message: 'Error processing data',
type: 'error',
autoClose: false,
actions: [{ label: 'View Details', displayType: 'accent' }]
});CLI Tool
The jupyterlab-notify command is installed with the extension:
# Basic notification (auto-detects URL from running servers)
jupyterlab-notify -m "Deployment complete" -t success
# Output: URL: http://127.0.0.1:8888/jupyterhub/user/alice | Type: success
# Notification sent: notif_1765552893662_0
# With explicit URL (e.g., JupyterHub)
jupyterlab-notify --url "http://127.0.0.1:8888/jupyterhub/user/alice" -m "Hello"
# Persistent warning (no auto-close)
jupyterlab-notify -m "System maintenance in 1 hour" -t warning --no-auto-close
# Silent mode (notification center only, no toast)
jupyterlab-notify -m "Background task finished" --auto-close 0URL auto-detection: Queries jupyter server list --json to find running servers and constructs localhost URL. Falls back to JUPYTERHUB_SERVICE_PREFIX environment variable or localhost:8888.
cURL
# Localhost - no authentication required
curl -X POST http://localhost:8888/jupyterlab-notifications-extension/ingest \
-H "Content-Type: application/json" \
-d '{"message": "Build completed", "type": "success"}'
# Localhost - warning that stays until dismissed
curl -X POST http://localhost:8888/jupyterlab-notifications-extension/ingest \
-H "Content-Type: application/json" \
-d '{"message": "System maintenance in 1 hour", "type": "warning", "autoClose": false}'
# Remote - requires authentication token
curl -X POST http://jupyterhub.example.com/user/alice/jupyterlab-notifications-extension/ingest \
-H "Content-Type: application/json" \
-H "Authorization: token YOUR_JUPYTER_TOKEN" \
-d '{"message": "Deployment complete", "type": "info"}'Architecture
Broadcast-only model - all notifications delivered to the JupyterLab server.
Flow: External system POSTs to /jupyterlab-notifications-extension/ingest -> Server queues in memory -> Frontend polls /jupyterlab-notifications-extension/notifications every 30 seconds -> Displays via JupyterLab notification manager -> Clears queue after fetch.
Troubleshooting
Frontend installed but not working:
jupyter server extension list # Verify server extension enabledServer extension enabled but frontend missing:
jupyter labextension list # Verify frontend extension installedNotifications not appearing: Check browser console for polling errors or verify JupyterLab was restarted after installation.
Uninstall
pip uninstall jupyterlab_notifications_extensionDevelopment
Setup
Requires NodeJS to build the extension. Uses jlpm (JupyterLab's pinned yarn) for package management.
# Install in development mode
python -m venv .venv
source .venv/bin/activate
pip install --editable ".[dev,test]"
# Link extension with JupyterLab
jupyter labextension develop . --overwrite
jupyter server extension enable jupyterlab_notifications_extension
# Build TypeScript
jlpm buildDevelopment workflow
Run jlpm watch in one terminal to auto-rebuild on changes, and jupyter lab in another. Refresh browser after rebuilds to load changes.
jlpm watch # Auto-rebuild on file changes
jupyter lab # Run JupyterLabCleanup
jupyter server extension disable jupyterlab_notifications_extension
pip uninstall jupyterlab_notifications_extension
# Remove symlink: find via `jupyter labextension list`Testing
Python tests (Pytest):
pip install -e ".[test]"
pytest -vv -r ap --cov jupyterlab_notifications_extensionFrontend tests (Jest):
jlpm testIntegration tests (Playwright/Galata): See ui-tests/README.md
Packaging
See RELEASE.md for release procedures.
