feat(vscode): support Jupyter notebook context#11532
Open
markijbema wants to merge 3 commits into
Open
Conversation
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Previous Review Summary (commit f004b49)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit f004b49)Status: 1 Issues Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)WARNING
Files Reviewed (10 files)
Reviewed by gpt-5.4-20260305 · Input: 42.3K · Output: 4.6K · Cached: 113.7K Review guidance: REVIEW.md from base branch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add Jupyter notebook awareness to the VS Code extension so Python code cells receive whole-notebook classic autocomplete context, while notebook files appear correctly in active, visible, and open editor context.
The notebook-cell assembly logic is imported from Continue in a provenance-only commit, then integrated separately with Apache-2.0 attribution and redistribution material. Markdown and non-Python cells are left unchanged rather than routing them through Python heuristics, and Next Edit remains file-only because applying notebook-wide edits back to individual cells requires a separate mapping design.
Built for Mark IJbema by Kilo for Slack