Hey @oula, thanks for the detailed report. The logs and the fact that you clearly separated your case from the old-kernel story really help.
You’re right, your case is different from what’s described in this thread. Here the root cause is tied to the linux-legacy-x64 build on an old glibc CentOS 7 or Debian 9. You’re on Ubuntu 22.04 with glibc 2.35 and the linux-x64 artifact, so it’s a different environment. This should be tracked separately even if the surface symptom looks the same Agent Execution Timed Out, cursor-agent-exec doesn’t activate, and the renderer sends terminate.
Your workaround is correct. Please stay on 3.14.27 until there’s an update.
So your case doesn’t get mixed with the legacy issue and can be tracked on its own, please open a separate thread for the linux-x64 glibc 2.35 variant. You can just move what you already wrote there. Also include the Request ID from the chat menu in the top right > Copy Request ID. If Privacy Mode is enabled, the ID might not be saved, then just say it’s enabled. A full remoteexthost.log from the remote host would also help.
Once you’ve created it, drop the link here and the team will pick it up.