zai-org / zai-org/feedback

[Bug] MCP 工具「始终允许(本项目)」不持久化——重启/新会话后再次弹窗

Open
#604 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

问题描述

MCP 工具权限弹窗选择「始终允许(本项目)」后不持久化——重启或新会话后同类调用再次弹窗,「始终允许」实际等同「仅此次允许」。

复现步骤

  1. 配置任一 MCP server(含工具);
  2. 调用其工具 → 权限弹窗 → 选「始终允许(本项目)」;
  3. 重启 ZCode(或新会话)→ 再次调用同工具 → 再次弹窗。

实测证据

本地权限持久化表(permission 相关存储)在多次「始终允许」后仍为 0 行——写入链路未落库(或读取不生效)。

期望行为

项目级 MCP allow 规则持久化,重启/新会话生效。

环境

ZCode 3.9.2 与 3.11.2 均复现 · Windows 10 26100

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

Trace the MCP permission write and read paths for the project-level “always allow” choice, starting with the permission-related local persistence mentioned in the report. Reproduce the prompt flow, confirm whether the rule is written, then restart or open a new session and verify that the same tool no longer prompts.

Written by the indexing model from the issue text.

Assessment

Domain
authorization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.