Kilo Code stumbles on Jupyter notebooks

Notebook support is still the sharpest edge in local coding assistants. That's partly an inference from the docs, but the thread makes the pain obvious once the workflow depends on notebook JSON, execution state, and editor refresh behavior. Kilo Code's docs emphasize code generation, refactoring, autocomplete, and agent workflows in VS Code, so notebook handling is more of a gap than a core promise. Continue still has the familiar Ctrl+I edit primitive for quick inline changes, which is why users remember it even when the rest of the extension felt buggy. Cline is the clearest notebook-first alternative because it advertises cell-level generate, explain, and improve actions while preserving notebook structure. A # %% split Python script is the pragmatic workaround when you want local LLM edits without fighting ipynb serialization. If notebook work is the main event, the best pattern is often edit in py, execute in the notebook, and only round-trip to ipynb at the end.