Settings no longer allowed in workspace

[g-arjones]

Since d9a5827 and e78a80c ,rubyLsp.customRubyCommand and rubyLsp.bundleGemfile are no longer allowed in the workspace configuration. How are users supposed to deal with projects having different activation commands and Gemfiles in different paths?

These are exactly the kind of settings you want to apply to workspaces.

[i10416]

I believe this is because rubyLsp.customRubyCommand is machine scope.

https://code.visualstudio.com/api/references/contribution-points#:~:text=A%20configuration%20setting%20can%20have%20one%20of%20the%20following%20possible%20scopes

If no scope is declared, the default is window.

The default scope is window, but d9a5827 changes every those scopes to machine

d9a5827 prevents untrusted workspace from executing arbitrary command via customRubyCommand, so it would be safe to set the scope to window.

[amarkowitz]

This issue is affecting our team, too.

[Splines]

As my issue #4124 was flagged as duplicate of this, I just want to give an overview again here of the bug we face and a workaround, which is unfortunately downgrading the VSCode extension.

🎈 Bug Description

The Ruby LSP Extension does not start correctly anymore when I open any Ruby file. In the extension logs, we see this

2026-06-04 12:27:01.431 [info] (mampf) Running command: ` && ruby -EUTF-8:UTF-8 '/home/mampf/.vscode-server/extensions/shopify.ruby-lsp-0.10.4/activation.rb'` in /workspaces/mampf using shell: /usr/bin/zsh

This fails due to the && in the beginning. Probably, the first part before the && got somehow lost or was set to a null value. This leads to this error during startup:

Automatic Ruby environment activation with custom failed: Command failed: && ruby -EUTF-8:UTF-8 '/home/mampf/.vscode-server/extensions/shopify.ruby-lsp-0.10.4/activation.rb' zsh:1: parse error near `&&'

The relevant part of our settings.json looks like this (see also here):

// settings.json (extract)
//////////////////////////////////////
// Ruby (RuboCop)
//////////////////////////////////////
"[ruby]": {
 "editor.defaultFormatter": "Shopify.ruby-lsp",
 "editor.formatOnSave": true
},
"rubyLsp.formatter": "rubocop",
// https://shopify.github.io/ruby-lsp/version-managers.html#custom-activation
"rubyLsp.rubyVersionManager": {
 "identifier": "custom"
},
"rubyLsp.rubyExecutablePath": "/usr/local/bin/ruby",
"rubyLsp.enabledFeatures": {
 "codeActions": true,
 "diagnostics": true,
 "documentHighlights": true,
 "documentLink": true,
 "documentSymbols": true,
 "foldingRanges": true,
 "formatting": true,
 "hover": true,
 "inlayHint": true,
 "onTypeFormatting": true,
 "selectionRanges": true,
 "semanticHighlighting": true,
 "completion": true,
 "codeLens": true,
 "definition": true
},
//////////////////////////////////////
// Ruby Test Explorer
//////////////////////////////////////
"rubyLsp.featureFlags": {
 "fullTestDiscovery": true,
},
"rubyLsp.addonSettings": {
 "Ruby LSP RSpec": {
 "rspecCommand": "env VITE_RUBY_PORT=3036 RAILS_ENV=test bundle exec rspec --format documentation"
 }
},

🎈 Workaround

Downgrading to version 0.10.3 of the VSCode extension and reloading the window afterwards fixes the problem, so this was probably introduced in the latest release. Note however, a team member reported that they also saw this problem on 0.10.3, so maybe one has to even further downgrade :(

2026-06-13 14:37:43.652 [info] (mampf) Running command: ` && ruby -EUTF-8:UTF-8 '/home/mampf/.vscode-server/extensions/shopify.ruby-lsp-0.10.3/activation.rb'` in /workspaces/mampf using shell: /usr/bin/zsh

[fosterfarrell9]

In the above settings, a monkey patch that works for us (in 10.4) is to replace
rubyLsp.rubyVersionManager.identifier: "custom" by "none", and in the VS Code machine settings (in our setup in ~/.vscode-server/data/Machine/settings.json) adding "rubyLsp.customRubyCommand": "export PATH=/usr/local/bin:$PATH".

[github-actions]

This issue is being marked as stale because there was no activity in the last 2 months