Hi thanks for filing this issue. I am able to reproduce this issue on the sample repo you gave, however I am not able to easily reproduce this because I can't put console logs or breakpoints to investigate the code that causes this issue.

@connor4312 I am currently trying to run VS Code and put logs there, then in the OSS instance open the sample extension and run the tests that the author mentions here using npm run test. This opens a new instance of VS Code and executes tests like the smoke tests we have. Do you know if there is a way to debug this on the VS Code side?

@leep-frog can you please create in the meantime a sample extension that reproduces this issue? This I can easily debug. I tried the following sample extension:

export async function activate(context: vscode.ExtensionContext) {
	console.log('Congratulations, your extension "testextension" is now active!');

	await vscode.commands.executeCommand("workbench.action.toggleDevTools");
	await delay(1500);
	await vscode.commands.executeCommand("cursorEndSelect");
	await delay(1500);

	console.log('before editor.action.clipboardCopyAction');
	
	await vscode.commands.executeCommand("editor.action.clipboardCopyAction");
	await delay(1500);
	await vscode.commands.executeCommand("cursorDown");
	await delay(1500);

	console.log('before editor.action.clipboardPasteAction');
	await vscode.commands.executeCommand("editor.action.clipboardPasteAction");
}

Which is essentially the same code you had, except it does not reproduce your issue.

Screen.Recording.2025-07-09.at.13.04.17.mov

editor.action.clipboardCopyAction command no longer works #243932

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`editor.action.clipboardCopyAction` command no longer works #243932