[che-code] When using clone path project are not added in the worktree

[batleforc]

Describe the bug

In Vscode, if you create a devfile using the clone path , the project does not appear inside of the vscode worktree and can't be found in the .code-workspace.

Che version

7.120@latest

Steps to reproduce

1. Create a workspace with this repo https://github.com/batleforc/weebo-che-project choosing vscode has the ide.
2. See that jb-plugin and jb-ide does not exist

Expected behavior

For those project to exist in the worktree.
The culprit seems to be https://github.com/che-incubator/che-code/blob/main/launcher/src/code-workspace.ts?rgh-link-date=2026-07-06T16%3A57%3A46.000Z#L156 it does not take into account the clone path if it exist.

Runtime

Kubernetes (vanilla)

Screenshots

No response

Installation method

other (please specify in additional context), chectl/latest, OperatorHub

Environment

Linux

Eclipse Che Logs

Additional context

No response

[svor]

@batleforc I assigned this issue to you since you've already opened a PR for it

[batleforc]

Hi @svor is it possible to have a review ? che-incubator/che-code#752

[rgrunber]

clonePathstring Path relative to the root of the projects to which this project should be cloned into. This is a unix-style relative path (i.e. uses forward slashes). The path is invalid if it is absolute or tries to escape the project root through the usage of '..'. If not specified, defaults to the project name.

Interesting, so this is a part of the devfile spec and we don't support it. I think this is a valid thing to fix 👍