Can't trigger rich completions for fish shell under WSL

[brettcannon]

Type: Bug

I opened an empty window, typed job like in the blog post announcing Fish support, and then pressed Ctrl+space to try and trigger the rich completions. Unfortunately I got a "Loading..." and then an error about how \home\brett can't be found (notice the incorrect slashes for Linux).

In the screenshot you can see the gutter decoration working, so shell integration is working.

VS Code version: Code - Insiders 1.102.0-insider (33ea51e, 2025-06-23T05:04:14.290Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 6.6.87.2-microsoft-standard-WSL2

System Info

Item	Value
CPUs	13th Gen Intel(R) Core(TM) i7-1370P (20 x 2189)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	63.66GB (41.83GB free)
Process Argv	--crash-reporter-id 8c2d3e93-0526-420f-a934-b71e879abff1
Screen Reader	no
VM	0%

Item	Value
Remote	WSL: Debian
OS	Linux x64 6.6.87.2-microsoft-standard-WSL2
CPUs	13th Gen Intel(R) Core(TM) i7-1370P (20 x 0)
Memory (System)	31.18GB (29.49GB free)
VM	0%

Extensions (13)

Extension	Author (truncated)	Version
codespaces	Git	1.17.3
remotehub	Git	0.64.0
vscode-todo-highlight	jgc	2.0.8
symbols	mig	0.0.24
theme-monokai-pro-vscode	mon	2.0.7
remote-containers	ms-	0.418.0
remote-wsl	ms-	0.99.0
remote-repositories	ms-	0.42.0
vscode-speech	ms-	0.16.0
copilot	Git	1.337.1641
copilot-chat	Git	0.29.2025062401
vscode-github-actions	git	0.27.2
vscode-pull-request-github	Git	0.113.2025062404

(1 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31249598
vscod805:30301674
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
dsvsc014:30777825
dsvsc015:30821418
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
dwnewjupytercf:31046870
pythonrstrctxt:31093868
nativeloc1:31118317
e80f6927:31120813
dwcopilot:31158714
c3hdf307:31184662
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31333650
g012b348:31231168
pythoneinst12:31251391
bgtreat:31252123
c7cif404:31309980
pythonpulldiag:31287486
6gi0g917:31259950
61ibe868:31282443
996jf627:31264550
pythonrdcb7:31268811
usemplatestapi:31297334
e6194696:31317039
747dc170:31275146
pythonfullctx:31296836
6518g693:31302842
generatesymbolt:31280541
convertfstringf:31280702
b99bg931:31306656
usemarketplace:31333563
0g1h6703:31329154
id45c886:31333049
nes-emitfast-1:31333560
d8gg1881:31333313
test-11-control:31334521

[Tyriar]

@meganrogge probably the same as #252026

[Tyriar]

@meganrogge also job wouldn't get picked up until we update:

vscode/extensions/terminal-suggest/src/shell/fishBuiltinsCache.ts

Lines 177 to 186 in c9015eb

	"if": {
	"shortDescription": "conditionally execute a command",
	"description": "if will execute the command CONDITION. If the condition's exit status\nis 0, the commands COMMANDS_TRUE will execute. If the exit status is\nnot 0 and else is given, COMMANDS_FALSE will be executed.\n\nYou can use and or or in the condition. See the second example below.\n\nThe exit status of the last foreground command to exit can always be\naccessed using the $status variable.\n\nThe -h or --help option displays help about using this command.\n\nEXAMPLE\nThe following code will print foo.txt exists if the file foo.txt\nexists and is a regular file, otherwise it will print bar.txt exists\nif the file bar.txt exists and is a regular file, otherwise it will\nprint foo.txt and bar.txt do not exist.\n\n if test -f foo.txt\n echo foo.txt exists\n else if test -f bar.txt\n echo bar.txt exists\n else\n echo foo.txt and bar.txt do not exist\n end\n\nThe following code will print \"foo.txt exists and is readable\" if\nfoo.txt is a regular file and readable\n\n if test -f foo.txt\n and test -r foo.txt\n echo \"foo.txt exists and is readable\"\n end",
	"args": "if CONDITION; COMMANDS_TRUE ...;\n[else if CONDITION2; COMMANDS_TRUE2 ...;]\n[else; COMMANDS_FALSE ...;]\nend"
	},
	"jobs": {
	"shortDescription": "print currently running jobs",
	"description": "jobs prints a list of the currently running jobs and their status.\n\njobs accepts the following options:\n\n-c or --command\n Prints the command name for each process in jobs.\n\n-g or --group\n Only prints the group ID of each job.\n\n-l or --last\n Prints only the last job to be started.\n\n-p or --pid\n Prints the process ID for each process in all jobs.\n\n-q or --query\n Prints no output for evaluation of jobs by exit status only.\n For compatibility with old fish versions this is also --quiet\n (but this is deprecated).\n\n-h or --help\n Displays help about using this command.\n\nOn systems that support this feature, jobs will print the CPU usage\nof each job since the last command was executed. The CPU usage is\nexpressed as a percentage of full CPU activity. Note that on\nmultiprocessor systems, the total activity may be more than 100%.\n\nArguments of the form PID or %JOBID restrict the output to jobs with\nthe selected process identifiers or job numbers respectively.\n\nIf the output of jobs is redirected or if it is part of a command\nsubstitution, the column header that is usually printed is omitted,\nmaking it easier to parse.\n\nThe exit status of jobs is 0 if there are running background jobs and\n1 otherwise.\n\nEXAMPLE\njobs outputs a summary of the current jobs, such as two long-running\ntasks in this example:\n\n Job Group State Command\n 2 26012 running nc -l 55232 < /dev/random &\n 1 26011 running python tests/test_11.py &",
	"args": "jobs [OPTIONS] [PID | %JOBID]"
	},

[meganrogge]

@Tyriar thinking to bring this fix back #251129

[Tyriar]

Can repro:

@meganrogge that fix was wrong though as what it was doing was meant to happen automatically which #251316 resolved (we thought). We need to look into it more.