Thank you very much for your help. I followed up on your suggestions and wanted to share the results.

1. Checking /workspaces

I inspected the recovery container:

• /workspaces/sistemas-dev exists but is empty.
• /workspaces/awp is missing.
• /workspaces/compliance is missing.
• A previous search for Git repositories under /workspaces found none.

These repositories were previously located under /workspaces, not in the container's home directory.

2. Checking the Dev Container configuration

On the develop branch, devcontainer.json does not specify remoteUser or containerUser.

The Dockerfile uses:

FROM mcr.microsoft.com/devcontainers/python:3.12-bullseye

This image normally uses the vscode user.

However, the creation log shows that GitHub attempted to restart an existing container and failed with:

unable to find user codespace: no matching entries in passwd file

The recovery container subsequently started successfully as vscode.

3. Checking the persistent storage

I inspected the current mount:

/codespacemount/workspace /workspaces rw,nodev,relatime master:256 - ext4 /dev/loop4 rw

The backing file for /dev/loop4 is:

/mnt/cloudenvdata/dockerlib

I still cannot determine whether this is the original persistent storage or a different filesystem state.

4. Rebuilding and backing up

I have not performed a rebuild because /workspaces is missing the original files, and I want to avoid any operation that could compromise recovery.

I also cannot run git stash or export the missing files using gh codespace cp, since the repositories and uncommitted files are not accessible in the recovery container.

The Codespace stopped unexpectedly while an AI coding agent was working. I have not yet found evidence that the agent modified the container configuration.

I have an open GitHub Support ticket (#4847245), but no response yet.

Given these results, do you think the codespace user error could be caused by GitHub's internal container configuration? More importantly, is there a safe way to verify whether the original workspace storage is still attached, without rebuilding the container?

I would really appreciate any additional ideas. Thank you again!