I've found that opening the folder in which the virtual environment was made allows VScode see the interpreter. When I open a subfolder I want to work on, without opening the parent folder in which the virtual environment was created, VScode won't see the interpreter.