zai-org / zai-org/feedback

[建议 / Feature] zcode:// 深链支持跳转到指定会话(可选:定位到具体消息)

Open
#326 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

提交前确认 · 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

我基于本地会话库(~/.zcode/cli/db/db.sqlite)自己写了一个会话检索/时间线工具,可以按项目、时间、标题搜到历史会话和具体某条消息。检索到之后想"一键跳回 ZCode 界面查看原文",但目前从外部唤起 ZCode 只能做到工作区粒度:zcode://workspace/open?path=...。想看某个具体会话只能在侧栏里手动翻找,长列表下很痛苦。

典型入口:终端命令、网页链接、脚本(例如从日志/报告里引用某次对话的某句结论)。

建议方案 · Proposal

扩展 zcode:// 深链路由表,例如:

  • zcode://session/open?sessionId=sess_xxx —— 在 ZCode 窗口中打开/聚焦指定会话
  • 可选进阶:&messageId=msg_xxx —— 定位并滚动到该会话的指定消息(message 表有稳定的 msg_* ID 和 sequence)

CLI 侧已有对称能力:zcode --resume <sessionId>

预期价值 · Expected value
  • 会话量大的用户(目前 40+ 个会话)从"检索到"到"打开看"从多次点击降为一次点击
  • 为第三方工具(会话检索、工作报告、Obsidian 类笔记引用)提供标准回跳入口,繁荣生态
  • CLI 与 GUI 能力对齐(CLI 已有 --resume)
你认为的优先级 · Your perceived priority

中 · Medium

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

v3.8.1 (3.8.1.5310) / macOS arm64

补充材料 · Additional context

据观察(v3.8.1),app 内部能力其实都已存在:侧栏切换、automations 运行记录里的"跳转到会话"、通知点击聚焦 task,走的都是内部的会话激活逻辑;zcode:// scheme 已注册且主进程深链路由表已成型(目前仅 workspace/open、oauth/callback、payment/callback 三条)。看起来只差把路由和内部会话激活能力接起来,实现成本应该不高。

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 existing zcode:// route table, workspace/open handling, and the internal session activation path mentioned in the issue. Compare these with the CLI --resume entry point and the session identifiers in ~/.zcode/cli/db/db.sqlite. Done means a session deep link opens or focuses the specified session, with message positioning handled if that option is included.

Written by the indexing model from the issue text.

Assessment

Tech stack
sqlite
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.