[FEATURE] Integrated file explorer panel in Cowork for single-monitor users
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
As a content creator who relies heavily on Claude for file-based workflows (writing scripts, generating text files, organizing project folders), I'd love to see an integrated file explorer panel within the Cowork interface — similar to VS Code's sidebar explorer.
Currently, to see files being created or edited in real-time during a Cowork session, I need to keep a separate Windows Explorer window open side-by-side. This works, but on a single monitor it cuts the usable space in half and requires constant window management.
I migrated from the Claude Code VS Code extension specifically because of performance issues (extension host memory pressure, UI freezes during file generation — see #23053, #14282). Cowork solved those problems, but I lost the integrated file visibility that VS Code provided.
Proposed Solution
Proposed Solution
A collapsible file tree panel on the side of the Cowork interface that:
- Shows the current project folder structure
- Updates in real-time as Claude creates, edits, or moves files
- Allows clicking a file to preview its contents
- Highlights recently modified files (e.g., with a subtle color or icon)
- Can be toggled on/off for users who don't need it
Why This Matters
Many users who moved from Claude Code in VS Code to Cowork did so because of stability — not because they preferred less visibility. An integrated explorer would make Cowork a complete replacement for the VS Code workflow, especially for:
- Content creators managing multi-file projects
- Single-monitor setups where split-screen is impractical
- Users who need to verify file output without leaving the interface
Current Workaround
- Windows Explorer snapped to half the screen alongside Claude Desktop
- Or using
Win + Arrowto tile windows manually
Environment
- Platform: Windows 11
- Plan: Pro
- Use case: YouTube content production pipeline (scripts, audio text, image prompts, metadata)
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗