jupyterlab_advanced_code_viewer_extension
You work in JupyterLab while an AI agent in the lab terminal writes the same notebooks and source files on disk. This extension shows the agent's changes in the open document as they are written, keeps your unsaved edits, and lets you direct the agent with comments stored in the file, where the agent reads and answers them.
It works while you edit. It runs inside the notebook and inside the file editor, adds no separate viewer and has no mode to enter: every function is active in a notebook's command mode and edit mode, in a rendered and in an unrendered Markdown cell, and in the file editor while you type. Settings switch single functions on and off.
It covers notebooks (.ipynb) and every text file the JupyterLab file editor opens, such as .py, .ts, .rs, .sh and .yaml. The first case it is built for: the agent executes a notebook with jupyter nbconvert --to notebook --execute --inplace, and the notebook you have open shows the new cells and outputs.
Features
- Changes show while you type - a change another program writes to the file shows in the open editor within half a second; added text is painted green, removed text is struck through on red
- Your edits are kept - a change from disk lands around your unsaved edits; where it overlaps them your text stands and the tab shows a red square
- Your place is kept - a change from disk moves neither the cursor nor the selection, takes no focus, keeps the text in view where it is, and never appears in your undo history
- No File Changed dialog - a disk change the extension has applied raises no dialog, and a save never overwrites a disk change it has not applied
- Notebooks change in place - cells added, removed, moved and changed on disk show in the open notebook, outputs and execution counts included; scroll position, selection, active cell and the kernel session stay
- Mark and comment on code - six colours, comment threads, notes on a passage or on the whole document, listed in a panel beside the editor and grouped by cell in a notebook
- Notes are stored in the file - as comment lines in the file's language, as HTML comments in a Markdown cell, as cell metadata for a stored output; a marker never changes what the program does
- Tab icons - a half-filled circle for a new change, a red square for a change held back, a cross for a deleted file
- Agent skill - teaches an AI assistant the marker form per language, where markers may go in code, and how to answer and close a comment
Sibling extensions
The extension brings the functions of two read-only viewers to code. Marks use the same grammar in all three, so an agent that knows one of them can work in each.
| Sibling | What it does | What this extension takes from it |
|---|---|---|
| jupyterlab_advanced_markdown_viewer_extension | Follows a Markdown file in the Markdown Preview, shows each change, and keeps marks and comments in the file as HTML comments | Following, change display, the rule for unsaved edits, tab icons, mark grammar, notes panel, agent skill, setting names |
| jupyterlab_advanced_html_viewer_extension | Shows an HTML file with trust and refresh, and adds the same marks and notes panel | The rule that only text written in the file takes a comment |
Releases
Following comes before marks, because a mark must stay on its text while the file changes.
| Release | What you can do when it is complete | Status |
|---|---|---|
| 1 | Type in a source file while an agent writes the same file; each change appears with the cursor in place and without JupyterLab's File Changed dialog | Not built |
| 2 | Keep a notebook open while an agent edits or executes it on disk; cells and outputs change in place | Not built |
| 3 | Mark a passage of a source file and write a comment; the agent answers in the same thread, and the marker does not change what the program does | Not built |
| 4 | The same in a notebook: Markdown cells, code cells and stored outputs | Not built |
Limitations
- Outputs that
jupyter nbconvert --executewrites come from another kernel process, so the kernel of the open notebook does not hold those variables - Text that a script or a widget draws in an output takes no comment; only text stored in the file does
- A file kind without a comment syntax, such as JSON or CSV, takes no mark
- A single change cannot be accepted or rejected on its own
- There is no separate read-only viewer for notebooks or source files
- Notes are stored in the document, never in a separate file beside it
- Each of the three extensions carries its own copy of the notes code; there is no shared package
Requirements
- JupyterLab 4.6 or later
Install
To install the extension, execute:
pip install jupyterlab_advanced_code_viewer_extension
Uninstall
To remove the extension, execute:
pip uninstall jupyterlab_advanced_code_viewer_extension
Metadata
Release files for jupyterlab-advanced-code-viewer-extension 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyterlab_advanced_code_viewer_extension-0.1.4.tar.gz | 236.6 kB | Without provenance | Details for jupyterlab_advanced_code_viewer_extension-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyterlab_advanced_code_viewer_extension-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for jupyterlab_advanced_code_viewer_extension-0.1.4-py3-none-any.whl |
Total release size: 274.8 kB
Release files / jupyterlab_advanced_code_viewer_extension-0.1.4.tar.gz
| Download URL | jupyterlab_advanced_code_viewer_extension-0.1.4.tar.gz |
|---|---|
| Size | 236.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f8e7865ba73232d42514df27f3a16428bae6b7246b7bf58acc5fd06859ccced
|
|
BLAKE2b-256 checksum How to use checksums |
6092f849c9e28d90d95b8c4dee2470b3dc8083294cabd17c01b346f243a6978a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Release files / jupyterlab_advanced_code_viewer_extension-0.1.4-py3-none-any.whl
| Download URL | jupyterlab_advanced_code_viewer_extension-0.1.4-py3-none-any.whl |
|---|---|
| Size | 38.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b388ac2655622c74516b5c4402fee2000d0e3776ee23a3009fd3d141d7d66b06
|
|
BLAKE2b-256 checksum How to use checksums |
d287aee6df70bfd51780a99ffe236cdb76dbe17982cb1c228f6768e82826cdab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Security for jupyterlab-advanced-code-viewer-extension 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.