Improve Explorer refresh and root folder discovery for workspace directories containing many Git repositories

[zhangliyin126]

Component

Both

Problem

Problem

When using CC Pocket with a workspace root such as:

codebase/
  repo-a/
  repo-b/
  repo-c/
  newly-cloned-repo/

where codebase itself is not a Git repository but contains many git clone projects, the mobile Explorer may not show newly added root-level folders.

For example, after running:

cd ~/codebase
git clone https://github.com/example/new-project.git

the new new-project/ folder may not appear in the mobile app’s Explorer unless the file list is refreshed, and in large workspaces it may still be missing.

Why This Happens

Explorer currently relies on a list_files snapshot from the bridge rather than real-time directory watching.

For non-Git workspace roots, the bridge recursively scans the filesystem and derives folders from returned file paths. This has a few side effects:

• Explorer does not automatically update when a new directory is created.
• Root folders are inferred from files, not listed directly.
• If the workspace contains many repositories, the scan can hit the current file limit before reaching newly cloned projects.
• A newly cloned repository may not appear if none of its files are included in the returned file list.

This makes Explorer feel stale when CC Pocket is used with a common “workspace folder containing many repos” layout.

Proposed solution

Requested Feature

Please improve Explorer behavior for large workspace directories containing multiple Git repositories.

Possible improvements:

• Add a manual refresh button in Explorer.
• Refresh the file list when the app resumes or when Explorer is reopened.
• Include root-level directories directly, instead of only deriving directories from file paths.
• For non-Git workspace roots, prioritize shallow/root-level directory discovery before deep recursive file scanning.
• Consider returning a separate directory listing API for Explorer, instead of reusing file mention/autocomplete file lists.
• Indicate when results are truncated due to scan limits.

Expected Behavior

If a user clones a new repository under the configured workspace root, the new folder should appear in Explorer after refresh, even if the workspace contains many other repositories.

Use Case

This is especially useful for users who set their Codex/CC Pocket root to a broad workspace directory like ~/codebase, ~/projects, or ~/Workspace, and frequently clone or create new repositories there.

Alternatives considered

No response

Additional context

No response