Jupyter Inline Code Generation

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

While working with Jupyter Notebooks, Cursor can no longer generate more than two lines of code. Previously I was able to prompt Ctrl+K inside a python cell and instruct about the code, which I wanted to be generated. Now it is stuck up to two lines.

Steps to Reproduce

  1. Create an Jupyter notebook .ipynb file
  2. In a code cell prompt for a code generation (i.e.Ctrl+K and instruct to create a Fibonacci sequence)
  3. Observe it generating two lines and
  4. Display a Generating… message

Expected Behavior

Generate the requested code in the cell I am working on

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Various combinations. No change.

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes

Hey @Peio_Popov

Thanks for reporting this. I can reproduce this when I run Cmd+K without highlighting any text first.

Obviously not the intended behavior. I’ll report this. :folded_hands:

1 Like

Dear Colin, thank you for taking care of this bug! Can you please provide an issue reference or any other means so I can track when it’s eventually resolved.

Thank you

There’s no public issue tracker that I can share, but I’ll do my best to follow-up here once there’s movement!

I see the same issue. Could we fix it please? Thank you!

1 Like

I have the same issue. Anyone found a solution?

This Jupyter code generation issue seems to be imgerging because of the the bug in this version of Cursor. You should try updating this version. ANd it will start working normally….

Has this issue fixed yet?

Also experiencing this. I noticed it first in a notebook, but it’s happening even on non-notebook files; was able to reproduce on a blank text file in an empty new project. I’ve been able to work around it for now by inserting a blank comment line and highlighting that before hitting cmd+k.