zai-org / zai-org/feedback

Allowing renaming a project and showing associated folder path in the project context menu + allowing to change it

Open
#428 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: 功能建议
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

提交前确认 · Pre-submission checklist
  • 我已搜索过现有 issue,确认这不是重复提议 / I searched existing issues and confirmed this isn't a duplicate.
  • 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

使用场景 · Use case

I renamed one of my project folders on disk (ReportingTotal → ReportingInfra,
following a git repo rename). In ZCode's project list there is no way to rename
a project or to re-point it to the new folder, so:

  • the project entry kept pointing to the old path;
  • opening it treated the folder as a new, empty project;
  • all task history for that project disappeared from the UI, because tasks are
    indexed in tasks-index.sqlite by absolute workspace path (workspace_key /
    workspace_path, meta_json.workspacePath, task_group_view_node_orders.node_key).
    I had to close ZCode and hand-edit setting.json + the SQLite index to get my
    2 historical tasks back. That's risky surgery most users can't do.
建议方案 · Proposal
  1. Project list: allow renaming a project (display name, independent of the
    on-disk folder name).
  2. Show the associated folder path in the project context menu / details.
  3. Allow changing the associated folder ("re-point to a moved/renamed
    directory"), updating every internal reference atomically: recentProjects,
    lastWorkspaceSession, task index keyed by workspace path, task ordering.
  4. When opening a project whose folder no longer exists, offer to locate the
    new path instead of silently starting a blank project at the old path
    (like IDEs do for moved projects).
预期价值 · Expected value

Folder/repo renames are routine maintenance. Today they silently orphan all
project task history, and recovery requires manual database editing with the
app closed. Native re-pointing removes perceived data loss (and support load);
a display-name rename decouples the UI label from the folder name.

你认为的优先级 · Your perceived priority

中 · Medium

你使用的 ZCode 版本 / 环境 · ZCode version / environment

3.6.5.4145 (Windows x64)

补充材料 · Additional context

Manual recovery performed (ZCode closed): setting.json (recentProjects,
lastWorkspaceSession) and tasks-index.sqlite (tasks.workspace_key/workspace_path,
meta_json.workspacePath, task_group_view_node_orders.node_key). Conversation
transcripts in ~/.zcode/cli are keyed by session id and were unaffected.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the project list and project context menu, then inspect setting.json and tasks-index.sqlite, especially recentProjects, lastWorkspaceSession, workspace_key, workspace_path, meta_json.workspacePath, and task_group_view_node_orders.node_key. Define the affected references and the missing-folder flow before changing them. Done means a project can be renamed or re-pointed while its task history and ordering remain available, and a missing folder offers relocation instead of opening a blank project.

Written by the indexing model from the issue text.

Assessment

Tech stack
sqlite
Domain
databases, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.