Why did you cancel the function of node shell entering the host? This function is simply wonderful. It’s a pity to cancel it. Now I have to use the 2025.9.151055-latest version, and set the lens as read-only, and it is forbidden to automatically update to the new version. ![]()
We didn’t actually cancel that feature! It was removed by accident.
Good news though: it’s already fixed on our dev branch and will be back in the next release. Thanks for your patience!
Excellent, looking forward to the new version.
@crothmann I understand that you primarily focus on Loop at the moment but this behaviour is just not right. You accidentally removed a essential feature 45 days ago. You then mentioned one month ago that it’s already on the dev branch again. One month later there’s still no release which renders the terminal for nodes useless.
Could you give us some information here on when to expect this feature back in Lens? Thanks.
Hi @jonnyb, thanks a lot for your message — and welcome to the community!
You’re absolutely right that losing this feature is very frustrating, especially if you rely on node shell in your daily work.
Just to recap and give a clear status update:
- This was not intentional, it was a regression.
- The fix is already merged and queued for an upcoming Lens Desktop release.
- I can’t share an exact date, but it’s planned to go out as part of our next regular release, not as a long-term “maybe”.
I really appreciate you (and others) speaking up about this and also your patience while we get it properly restored. As soon as the Lens version with the fix is publicly available, I’ll come back to this thread and post the exact version number so you can safely upgrade.
Just to clarify: the node shell feature itself wasn’t removed and still works in general – the current bug affects only the the mounts and other permissions of the shell.
We absolutely understand how disruptive this is if you depend on node shell day to day, and I’m really sorry for the inconvenience. We’ve already identified and fixed the issue internally and are preparing a hotfix release for Lens Desktop in the coming days.
As soon as that version is publicly available, I’ll update this thread so you can upgrade with confidence.
Quick update: we’ve just shipped a patch release Lens-2025.12.101934-latest that restores the Node Shell behavior.
You can download the fixed build right now from our homepage:
If you run into any remaining edge cases after upgrading, please reply here with details/logs — feedback is very welcome and helps us make sure this stays solid across environments.