Skip to content

Add a Command Palette action to reload Wildtree #10003

@bholmesdev

Description

@bholmesdev

Summary

Add a Command Palette action to reload Wildtree / the File Tree so users have a deliberate way to reconcile the explorer with disk when automatic refresh misses a filesystem change.

Problem

A user reported that the file tree does not always refresh after terminal commands that change the filesystem, especially when the opened directory does not have a .git directory. One example they noticed is running a CLI deletion command on a directory and not seeing the file explorer update afterward.

This has not been reproduced locally yet, so the underlying automatic-refresh failure is still uncertain. Regardless, when the tree appears stale there is currently no obvious Command Palette action for the user to force Wildtree to reload. A visible toolbar refresh button would likely feel too heavy or janky for the file tree, but a Command Palette action would provide an explicit recovery path without adding persistent UI chrome.

Warp's file tree documentation says the tree automatically reflects project structure as files are added, removed, or changed, so this action should be a fallback rather than the primary refresh mechanism.

Expected behavior

  • The file tree continues to refresh proactively when terminal commands or filesystem watchers detect added, removed, or changed files.
  • If the tree appears stale, users can open the Command Palette and run an action such as Reload File Tree, Refresh File Tree, or Reload Wildtree.
  • The action reloads Wildtree from disk for the current project/session, including directories that are not Git repositories.

Actual behavior

  • A user reported that the file tree can remain stale after some terminal filesystem changes, including a CLI directory deletion.
  • The report specifically calls out cases where there is no .git directory.
  • There does not appear to be an obvious Command Palette action to reload Wildtree / the File Tree when this happens.

Reproduction steps or desired workflow

Reported scenario:

  1. Open Warp in a directory with the file tree visible.
  2. Use a directory that may not contain a .git directory.
  3. Run a terminal command that changes the filesystem, such as deleting a visible child directory from the CLI.
  4. Observe that the file tree may not update to reflect the deletion.

Desired workflow:

  1. Open the Command Palette.
  2. Search for a file-tree reload action, for example Reload File Tree or Reload Wildtree.
  3. Run the action.
  4. Wildtree reloads from disk and the file tree reflects the current filesystem state.

Artifacts

None attached.

Warp version

v0.2026.05.01.15.43.dev_00

Operating system

macOS 26.3.1 (build 25D771280a)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:searchGlobal search, command palette, and content discovery.area:workspaceFile tree, workspace navigation, project switching, and working-directory management.bugSomething isn't working.duplicateThis issue or pull request already exists.enhancementNew feature or request.in-app-feedbackFeedback items sourced from in-app feedback flows.os:macmacOS-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions