Mood: 😔
Category: Bugs

Title: Restoring an archived worktree session leaves it anchored to a stale, empty folder (breaks file tools + custom-agent discovery)

Affected version: 1.0.66-1 (desktop app, Windows)

Describe the bug

After restoring a worktree-backed session from archive, the session's working directory still points at the original generated worktree folder, but the actual git worktree has been re-created under a different (branch-named) folder. The original folder is left as an empty, non-git stub, so the session is anchored to a dead directory.

Steps to reproduce

1. Create a worktree-backed session (generates a folder, e.g. <worktrees>/<generated-name>).
2. Rename the branch early in the session (folder and branch names now diverge).
3. Archive the session, then later restore it from archive.
4. git worktree list shows the worktree at <worktrees>/<branch-name>, but the session's working directory is still <worktrees>/<generated-name> — now empty (no .git, no repo content, no .github/agents/).

Impact

• File/edit/glob tools default to the dead path and fail until absolute paths to the real worktree are used.
• Custom agents are discovered from <cwd>/.github/agents/; because cwd is the empty stub, all custom agents vanish from in-session tooling (only built-in agents remain) — even though the app UI still lists them.
• Shell commands default to the wrong directory.

Expected behavior

On restore, the session's working directory should be updated to the worktree's current path (or the worktree restored at the path the session references), so file tools and .github/agents/ discovery keep working.

Workaround

Restart/reopen the session to re-anchor cwd; until then, pass absolute paths to the real worktree.

Possibly related

• the right side panel to view files and terminal is not shown until I sent a m... #3931 (worktree/cwd divergence affecting resume)
• File diffs are undreadable if line length exceeds content width. #3528 (agent starts in wrong cwd)