zai-org / zai-org/feedback

[建议 / Feature]

Open
#535 1 comment 0 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

性能 · Performance (延迟 / 卡顿 / 资源占用)

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

使用场景 · Use case

环境:ZCode Desktop 3.11.2 / Windows 10.0.26200 x64

我在安装时把程序装到了 D 盘,但发现 ~/.zcode 数据目录仍固定在 C 盘用户主目录下,且无法在安装器或应用设置中更改。重度使用两个月后该目录已达 5.7GB(其中 cli/agents/ 下 66 个会话的 transcript.jsonl 占 4.7GB,单会话最大 1.3GB——每次模型请求的完整上下文都会重复落盘),C 盘空间压力大。

建议方案 · Proposal

安装器增加「数据目录」选项,或在应用设置中提供迁移入口;
迁移时自动搬移现有数据(credentials、会话历史等);
目前虽可通过 ZCODE_HOME 环境变量或 config.json 的 storage.dir 重定向,但完全无文档且用户不可感知,希望能正式化并在文档中说明。
另外建议提供 transcript 的自动清理策略(如按会话年龄/大小上限),供参考。

以上内容均由glm5.3-flash生成。

预期价值 · Expected value

No response

你认为的优先级 · Your perceived priority

None

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

No response

补充材料 · Additional context

No response

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 by tracing the existing ZCODE_HOME environment variable and config.json storage.dir behavior in ZCode Desktop. Review how the installer and application settings currently handle data locations, and document the existing relocation options. Done should include an agreed migration entry point, preservation of credentials and session history, and user-facing documentation; transcript cleanup is an additional proposal.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.