[Bug]: Worktree view hides staged files

[niallobrien]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

If I stage files in my editor, they disappear from T3Code's working tree view. Is this intentional?

Expected behavior

Working tree shows both staged and unstaged files.

Actual behavior

Staged files disappear from the working tree.

Impact

Minor bug or occasional failure

Version or commit

No response

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[juliusmarminge]

Thanks for the report — hiding staged files from Working tree is not intentional.

Working tree is a combined uncommitted view (HEAD vs the current tree): staged, unstaged, and untracked. It is not git diff / index-vs-worktree. Status already uses git diff HEAD --numstat for that combined total (#4843), and mobile even subtitles the section “Tracked, staged, and untracked worktree changes.” The web control is labeled Working tree; the client still names that scope unstaged, which is leftover naming, not a separate unstaged-only mode.

The known case where staging does make files vanish is a repo with no first commit. Staging turns untracked files into index entries, git diff HEAD fails on an unborn branch, and the failure is swallowed so review omits them. That hole is PR #10581.

This is not a duplicate of:

• #4022 — empty Working tree/Branch because packaged desktop validates cwd against $HOME
• #6139 — the feature that added the Working tree surface
• #9070 — commit generation rewriting the index

To confirm the path: does this repo already have a commit when the files disappear? If not, #10581 is the fix. If yes, please say so (and which surface: Diff → Working tree vs commit file list) so we can treat born-HEAD disappearance as a separate bug.

Accepted as a minor review/diff bug. Shared server+client review path, not desktop-only.

[niallobrien]

No, there is no existing commit, so staging/unstaging shows/hides the files from the working tree in T3Code. I cannot confirm if this behaviour also exists for branches with existing commits as I only tested against my current branch which doesn't have any existing commits.