jlabx

Launch JupyterLab with extensions — without touching your project's dependencies. Works with both uv and pixi projects.

uv tool install jlabx
jlabx

Why?

You're working in a repo with a pyproject.toml or pixi.toml, but you want JupyterLab with vim bindings, LSP, collaboration, and other extensions. You can't (or don't want to) add them as project dependencies. jlabx manages extensions separately and injects them at launch time — auto-detecting whether you're in a uv or pixi environment.

Quick start

# Install
uv tool install jlabx

In a project with a pyproject.toml or pixi.toml:

jlabx

Launch a single notebook — imports are auto-detected and mapped to PyPI packages:

jlabx analysis.ipynb

# Persist auto-detected deps as PEP 723 metadata in the notebook
jlabx notebook.ipynb --init-deps

# Force uv even in a pixi project
jlabx --uv

# Manage extensions
jlabx list                  # Show configured extensions
jlabx add jupyterlab-vim    # Add an extension
jlabx remove jupyterlab-vim # Remove an extension

Core extensions (always included)

• jupyterlab
• jupyter-collaboration
• jupyter-lsp
• python-lsp-server

Environment detection

jlabx auto-detects your environment:

Config

Extensions are stored in ~/.config/jlabx/config.toml (or $XDG_CONFIG_HOME/jlabx/config.toml). Created automatically on first run.

Documentation

Full docs: https://ianhi.github.io/jlabx/

License

MIT