Assistants are good at writing the contents of a cell and bad at getting it into the notebook, so the last step is usually a paste and a scroll. This closes that loop on the file itself: the assistant adds the cell, fixes the one above it, and reads the output your last run left behind. Execution stays on your side, which is also why nothing here can set a cell running by accident.
A server that treats an .ipynb file as a document rather than as a running kernel. You point it at a directory once, and after that the assistant can list the notebooks it finds there, create new ones, read a whole notebook or a single cell, replace a cell's source in place, and add code or markdown cells at a position you name. It also reads back the outputs already stored in a notebook, so an assistant can see what your last run produced. Nothing here executes anything — it edits the file, and the kernel stays yours.
- A workspace directory set once, after which every call works in paths relative to it
- The notebooks in that directory, listed
- A new empty notebook created at a path you name, with a title
- A whole notebook's structure and content read back, or one cell by index
- A cell's source replaced in place, and new code or markdown cells added at an index or at the end
- The stored outputs of every code cell in a notebook, or of one cell, read back without running anything