[建议 / Feature] Persistent file explorer sidebar in the desktop app(桌面端常驻文件树侧边栏)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
类别 · Category: UI / 界面体验 · UI / UX
Agent 框架 · Framework: 通用(桌面端外壳 · desktop app shell)
中文
问题描述 · Problem
ZCode Desktop 目前浏览项目文件结构只有 quick-action 菜单里的 Files(Ctrl+P),这是一个 quick-open / 搜索面板,而不是常驻的文件树。想查看项目的文件夹结构时,只能退回到外部资源管理器(Windows 资源管理器 / VS Code)并排使用,这样无法在 Agent 创建、修改文件的同时直接在 ZCode 内看到文件树的变化。
使用场景:长时间运行的 Agent 任务会涉及大量文件的创建和修改(例如多文件重构、代码审计)。用户需要常驻的文件树面板实时观察变化、点击打开文件,而不必离开应用。
建议方案 · Proposal
增加一个可固定(pinnable)的常驻文件资源管理器侧边栏,类似 OpenAI Codex Desktop 和 DeepSeek harness 的做法:
- 常驻面板(或一键切换)显示当前工作区的文件 / 文件夹树
- 点击打开文件,文件夹可展开 / 折叠,Agent 创建或修改文件时实时刷新
- 右键操作:新建文件 / 文件夹、重命名、删除、复制路径
环境 · Environment
- ZCode Desktop 3.14.0.7681(Windows)
- 工作区位于 WSL2 (Ubuntu)
English
Problem
In ZCode Desktop the only way to browse project files is the Files (Ctrl+P) entry in the quick-action menu, which is a quick-open/search palette — not a persistent file tree. To see the project structure, users fall back to an external file explorer (Windows Explorer / VS Code) side by side, and cannot watch the workspace tree change while the agent creates and edits files.
Use case: long-running agent sessions that touch many files (multi-file refactors, security audits). A persistent tree panel would let users watch changes land in real time and click to open a file without leaving the app.
Proposal
Add a persistent, pinnable file explorer sidebar for the active workspace, similar to the OpenAI Codex desktop app and DeepSeek's harness UI:
- always-visible panel (or one-click toggle) showing the workspace file/folder tree
- click to open a file; folders expand/collapse; live refresh as the agent creates/edits files
- context actions: new file/folder, rename, delete, copy path
Environment
- ZCode Desktop 3.14.0.7681 (Windows), workspace on WSL2 (Ubuntu)
Pre-submission: searched existing issues for "explorer sidebar" / "文件树 / 文件管理器" — no duplicates found.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named in the issue; first locate the desktop shell and its existing Files (Ctrl+P) flow. The scope includes a pinnable workspace tree, file opening, live refresh, and context actions, so completion requires defining and implementing the feature across the relevant desktop UI and workspace integrations.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100