Newly Created Python Notebooks Fail to Apply Changes in Composer

[colesmcintosh]

When attempting to create new Python notebooks, the file is successfully generated; however, during the subsequent apply operation, no modifications are made to the file. Ultimately, the process is canceled within the composer, leaving the notebook in an unaltered state. This behavior indicates a malfunction in the application logic when handling newly created Python notebooks.

Steps to Reproduce:

1. Create a New Notebook:
   • In the composer, initiate the creation of a new Python notebook.
   • Confirm that the file is successfully generated.
2. Apply Changes:
   • Proceed with the apply operation intended to integrate code or changes into the notebook.
3. Observe the Outcome:
   • Notice that despite the notebook file existing, no changes are applied.
   • The composer cancels the operation without modifying the file.

Expected Behavior:

Upon applying, the new Python notebook should be updated with the intended code or modifications, seamlessly integrating all changes without interruption.

Actual Behavior:

• The notebook file is created without error.
• The apply operation fails to update the notebook, effectively leaving the file unchanged.
• The composer then cancels the apply process, resulting in no effective change.

Additional Context:

• The issue appears specific to newly created Python notebooks.
• There are no explicit error messages indicating the cause of the failure.
• The malfunction disrupts the workflow, necessitating immediate investigation and remediation.

Environment:

• Cursor Version: 0.45.11
• VSCode Version: 1.96.2
• Operating System: Mac OS Sequoia 15.2

I kindly request an examination of the apply mechanism within the composer to identify and rectify the malfunction that prevents updates to newly created Python notebooks.

[SmileyJames]

I am also experiencing this issue: Version: 0.45.17 VSCode Version: 1.96.2 Commit: 7c00f62dd81412c8defe2b64b4d32d06e0a7e720 Date: 2025-02-26T19:15:49.861Z Electron: 32.2.6 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Darwin arm64 21.6.0

macOS Monterey Version 12.5.1 MacBook Air (M1 2020)

[vbalashi]

Same issue when using 'Edit mode' (ex-Composer)

Version: 0.46.11 (user setup) VSCode Version: 1.96.2 Commit: ae378be9dc2f5f1a6a1a220c6e25f9f03c8d4e10 Date: 2025-03-07T07:01:25.026Z Electron: 32.2.6 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Windows_NT x64 10.0.26100

[gudzenkov]

Same issue with both Agent and Manual mode

Version: 0.48.9 VSCode Version: 1.96.2 Commit: 61e99179e4080fecf9d8b92c6e2e3e00fbfb53f0 Date: 2025-04-12T18:33:49.349Z (6 days ago) Electron: 34.3.4 Chromium: 132.0.6834.210 Node.js: 20.18.3 V8: 13.2.152.41-electron.0 OS: Darwin arm64 23.6.0