Task extension conflicts with VS Code native "Tasks: Run Task" functionality

[davidjlbailey]

• Task version: 0.4.0
• Operating System: Ubuntu 24.04

If the extension is installed but disabled on launch, built in tasks work as expected ie Shift+Ctrl+P "> Tasks: Run Task" shows all tasks in tasks.json (and those added by extensions). The task selected via the command palette run as expected

If I then enable the extension, and repeat, tasks from tasks.json are shown (but others are missing). If I select a task in tasks.json from the command palette, I get an error "Cannot read properties of undefined (reading 'shell')" in a VSCode Notification

I can minimally reproduce this with VS Code running locally with no other extensions enabled and the following tasks.json file as the only file in the project (in the .vscode folder)

{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "shell",
			"label": "echo test",
			"command": "echo",
			"args": ["test"],
			"group": "test",
		}
	]
}

Possible duplicate of #122

---

VS Code
Version: 1.104.3
Commit: 385651c938df8a906869babee516bffd0ddb9829
Date: 2025-10-02T12:30:51.747Z
Electron: 37.3.1
ElectronBuildId: 12404162
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Linux x64 6.14.0-33-generic snap

Extension
task.vscode-task
Version 0.4.0
Last Updated 2025-10-08, 19:52:22

[davidjlbailey]

I've fixed the issue (for my test case above) in a local fork of the extension.

The problematic line is package.json:L271 (in v0.4.0)

The naming of the field "task" under properties is conflicting with the settings for the built in Tasks functionality (which are also prefixed with "task." in settings.json).

If this name is changed to "vscode-task", say, then the built in tasks functionality works as expected.

I haven't worked out which setting specifically is causing the observed behavior, as the general fix removes all conflicts.

[davidjlbailey]

Which I've just seen you've fixed in 'main'... So, nothing to do, and I'll just wait for the next update!