Recurring Git Index Corruption in Google AI Studio App Workspaces

Summary

Google AI Studio app-development workspaces have repeatedly developed a corrupted Git index while working with an existing GitHub repository.

This has now occurred in more than one AI Studio applet/workspace, making the built-in repository unusable for normal Git operations.

Error

The recurring error is:

fatal: unknown index entry format 0xbd040000

The affected repository has been reported by AI Studio at paths including:

/app/applet

and later described as:

the root repository in /

Date observed

The repeated incidents occurred on July 31, 2026 NZST.

Repository

M-TEKA-T-A-MXZTAR/Doctor_Tee_Web-side-sub-system

Workflow at the time

Google AI Studio was:

  • editing an existing GitHub-connected TypeScript/React repository;
  • creating a feature branch;
  • committing incremental changes;
  • pushing those commits using the GitHub credential stored securely in project secrets;
  • updating an existing draft pull request.

The active feature branch was:

feat/level-1-1-store-editor-public-storefront

The draft pull request was:

PR #239

Recovery performed

Because the original AI Studio checkout could no longer perform normal Git operations, the work had to be recovered into clean clones under temporary paths such as:

/tmp/clean_repo
/tmp/clean_repo_2

The source changes were preserved, committed and pushed from those clean clones.

The remote GitHub repository remained intact.

The latest preserved remote feature-branch commit at the time development was paused was:

5ffd198da0808d862d3cefcf68e2d9ec9344571f

Recurrence

This was not a single isolated failure.

A second AI Studio applet/workspace produced the same or equivalent corrupted-index warning after development continued from a clean clone.

This suggests a possible issue with the AI Studio workspace filesystem, repository initialization, persisted Git metadata, or concurrent background Git operations.

Impact

The issue:

  • prevents normal use of git status, git diff, branch switching and commits in the original workspace;
  • requires manual repository recovery;
  • risks losing uncommitted work;
  • forces continued development into transient /tmp directories;
  • makes it unsafe to continue development in AI Studio;
  • has caused the project to pause pending investigation.

Remote repository safety

The GitHub repository itself does not appear corrupted.

The draft PR remained:

  • open;
  • unmerged;
  • mergeable;
  • based on the correct main commit;
  • accessible through GitHub.

The problem appears limited to AI Studio’s local workspace Git metadata.

Requested investigation

Please investigate:

  1. Whether AI Studio performs concurrent background Git operations while an agent is also running Git commands.
  2. Whether workspace persistence or cloning can copy a malformed .git/index into another applet.
  3. Why a project repository was reported as rooted at /.
  4. The filesystem type and mount behaviour used by the affected applets.
  5. Whether disk, inode, container restart or interrupted-write events occurred.
  6. Whether .git/index.lock or multiple Git processes existed near the failures.
  7. Whether the same persisted storage or template was reused across both affected applets.

Where available, please preserve and inspect:

  • workspace/app identifiers;
  • timestamps;
  • Git version;
  • repository root;
  • .git/index size and modification time;
  • SHA-256 of the damaged index;
  • first 64 bytes of the index in hexadecimal;
  • .git/index.lock metadata;
  • background Git-operation logs;
  • filesystem and container event logs.

Safety actions already taken

Development in Google AI Studio has been paused.

The corrupted workspaces have not been repaired with:

rm .git/index
git reset

because this could destroy evidence needed to diagnose the recurring issue.

No secrets, tokens, authenticated remote URLs or environment-variable values are included in this report.