[BUG] Unable to select configuration profile after VS Code update

[AndersHogqvist]

Describe the bug
I updated VS Code to 1.110.1 and now I get No workspaces with Robot Framework files found. when I try to select configuration profile.

Steps To Reproduce
Steps to reproduce the behavior:

1. Open a workspace with Robot Framework files and a robot.toml containing a couple of profiles
2. Run RobotCode: Select Configuration Profiles

My robot.toml:

# Default settings
log-level = "DEBUG"
output-dir = "src/Export/TestFiles/log"
debug-file = "debug.txt"

[variables]
EXPORT_FOLDER = "src/Export"
DEFAULT_IP_FOLDER = "doc/Default IP file"
TEST_FOLDER = "src/Export/TestFiles"
LOG_FOLDER = "src/Export/TestFiles/log"

[profiles.base]
args = ["--pythonpath", "HIL-rig/libs", "--pythonpath", "HIL-rig/keyword_libs"]

[profiles.rae1]
inherits = "base"
extend-variables = { HIL = "RAE 1", DEFAULT_IP_FILE = "RAE_v3.ip" }
extend-includes = ["rae"]

[profiles.rae2]
inherits = "base"
extend-variables = { HIL = "RAE 2", DEFAULT_IP_FILE = "RAE_v3.ip" }
extend-includes = ["rae"]

[profiles.saicb1]
inherits = "base"
extend-variables = { HIL = "SAICB 1", DEFAULT_IP_FILE = "SAICB.ip" }
extend-includes = ["saicb"]

[profiles.saicb2]
inherits = "base"
extend-variables = { HIL = "SAICB 2", DEFAULT_IP_FILE = "SAICB.ip" }
extend-includes = ["saicb"]

[profiles.saicb3]
inherits = "base"
extend-variables = { HIL = "SAICB 3", DEFAULT_IP_FILE = "SAICB.ip" }
extend-includes = ["saicb"]

# Robocop linter config
[tool.robocop.lint]
configure = ["too-many-calls-in-test-case=false"]

Expected behavior
I get the menu where I can choose profile.

Logs
RobotCode output:

executeRobotCode: exit code 0
client for file:///c%3A/Dev/auto-uac stopped.
executeRobotCode: c:\Dev\auto-uac\.venv\Scripts\python.exe -u -X utf8 c:\Users\SEANHOG1\.vscode\extensions\d-biehl.robotcode-2.2.0\bundled\tool\robotcode --format json --no-color --no-pager -dp . profiles list
create Language client: RobotCode Language Server for folder auto-uac
trying to start Language client: RobotCode Language Server for folder auto-uac
client for file:///c%3A/Dev/auto-uac starting.
executeRobotCode: exit code 0
client for file:///c%3A/Dev/auto-uac running.
client for file:///c%3A/Dev/auto-uac started.
executeRobotCode: c:\Dev\auto-uac\.venv\Scripts\python.exe -u -X utf8 c:\Users\SEANHOG1\.vscode\extensions\d-biehl.robotcode-2.2.0\bundled\tool\robotcode --format json --no-color --no-pager -dp . profiles list
executeRobotCode: c:\Dev\auto-uac\.venv\Scripts\python.exe -u -X utf8 c:\Users\SEANHOG1\.vscode\extensions\d-biehl.robotcode-2.2.0\bundled\tool\robotcode --format json --no-color --no-pager -p base -p saicb2 -dp . discover --read-from-stdin all -P HIL-rig/libs -P HIL-rig/keyword_libs
executeRobotCode: exit code 0
executeRobotCode: exit code 0

RobotCode Language Server output:

[Error - 1:46:39 PM] Server process exited with code 0.

Additional context
This has been working perfectly until today and I haven't changed anything. Also, I can still run tests as usual.

Desktop (please complete the following information):

• VS Code Version 1.110.1
• RobotCode Version 2.2.0
• OS: Windows
• Python Version 3.11.9
• RobotFramework Version 7.4.2
• RoboCop 8.2.2
• RobotFramework Tidy 4.18.0

[jannekSympa]

Having also same issue

vscode version:

Version: 1.111.0 (user setup)
Commit: ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb
Date: 2026-03-06T23:06:10Z

RobotCode Version: 2.2.0
Robot Framework Version: 7.3.2
Python Version: 3.12.11 
Robocop Version: 7.2.0
OS: Ubuntu 24.04

[erikmeijer91]

We have the same issue.

vscode version

• 1.111.0
• ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb
• x64

OS:

• robotcode: 2.2.0
• python: 3.13.12
• robotframework: 7.1.1
• os: Windows

[jandubcak-eset]

For all that would like to switch profiles in the meantime. You can downgrade VSCode to lower version.
Version 1.0.9 worked for me.
Kill VSCode, download x64 package, install it (this will downgrade the VSCode version) run as usual (my IDE configuration was persisted and not lost).
Select configuration profiles as before. Profit.

[NickAssink-Inspiro]

We have a project that is not using a robot.toml file, but we have the same issue.
As suggested by jandubcak-eset downgrading vs-code will resolve the issue for now.

[d-biehl]

sorry, cannot reproduce it. it is working fine on my side with and without robot.toml and profiles.

Did you try to reassign the python interpreter to your project? Press F1 and then execute the `Python: Select Interpreter' command and then select the correct one.

Do you use virtual python environments? What python project/package manager do you use for your project?

[AndersHogqvist]

sorry, cannot reproduce it. it is working fine on my side with and without robot.toml and profiles.

Sorry but I don't understand what you're saying here. Are you able to select configuration profiles without having any profiles? How is it even possible to select a configuration profile without a robot.toml with profiles in it? I thought that was the only place where you could define configuration profiles.

But to test your suggestions I removed my .venv folder, created a new virtual env in which I installed all the dependencies and selected it in VS Code, it didn't solve the issue. We're not using any particular project/package manager, just a simple requirements.txt.