I noticed that since today (or maybe yesterday) freshly created codespaces launch the terminal in the wrong directory. As you can see from attached screenshot, the codespace gets launched in the
workspace directory and not in the directory that actually contains the cloned project. I am basically one level too high.
cd on the terminal and work on the project, but the issue is that being in the parent directory breaks some project configs, e.g. for ESLint. I am not sure when exactly this problem started but I think I can narrow it down to today or yesterday.