I’m trying to use Cursor 3 even more, but am getting stuck when using it on python repos as the LSP isn’t working correctly so I can’t do the things I’d like to - ‘Go to definition’ or see the type hints and docstrings.
In the editor window, i’m was able to select the venv and have a lot more clarity on the python language server, extension settings etc, but I have no clue how to configure any of that in Cursor 3.
If you could let me know how to setup my projects so that the LSP works that would be immensely helpful.
The Agents Window does support Python language features. Here’s how to get them working:
Enable the LSP toggle – when you have a Python file open in the Agents Window, look for the LSP toggle in the top-right corner of the file tab. Make sure it’s enabled. This loads the Python and Pylance extensions.
Configure your Python interpreter – the Agents Window doesn’t have the same interpreter selector as the editor window. To point it at your venv, add this to your project’s .vscode/settings.json:
Replace the path with the actual path to your virtual environment’s Python binary. Once this is set, the Pylance extension should pick up the venv and provide type hints, docstrings, and Go to Definition.
If features still aren’t working after enabling LSP – try closing the file tab and reopening it. The LSP auto-enables when a code file is opened, but sometimes the extensions need a moment to activate.
That said, the Agents Window is still relatively new and extension support is being actively expanded. Some LSP features may not work as smoothly as in the editor window yet. For full Python IDE functionality (interpreter selection UI, all Pylance features), the editor window remains the more complete experience. You can use both side by side.