1jehuang / 1jehuang/jcode

在 Jcode 对话中,当 AI 回复内容较长(例如代码扫描报告、架构分析等),系统会自动折叠/收起回复,用户无法直接看到结论性内容。需要手动展开才能阅读,严重影响使用体验。

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

Nobody has claimed this yet.

enhancement priority: medium triage: needs-decision
Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
30

Description

本会话中发生了 3 次,每次 AI 都不得不把结论写到外部文件中让用户打开查看:

案例 1:权限代码扫描报告
AI 输出了 7 个问题的完整扫描报告(包含表格、代码片段、分级标题)
被折叠 → 用户问"我的结论在哪里看呢"
最终写入 权限代码扫描报告.md 文件解决

案例 2:Fix Plan 方案
AI 输出了修复 @Async 问题的 Plan
被折叠 → 用户反馈"又被折叠了"
最终写入 fix-async-security-plan.md 文件解决

案例 3:修复审查结论
AI 输出了 TaskDecorator 方案的审查结论(对比表格)
被折叠 → 用户反馈"结论看不到"
最终写入 async-fix-review.md 文件解决

预期行为

长回复应默认展开关键结论部分(摘要/结论在前几行可见)
或提供配置选项:用户可选择"始终展开"/"折叠长回复"的阈值
或采用"结论先展示 + 详情折叠"的分层展示模式

触发条件

回复中包含表格(Markdown table)
回复中包含代码块
回复总行数超过一定阈值(目测约 30-40 行)

建议修复方向

智能摘要:折叠时保留前 N 行作为摘要可见(如结论/总结部分)
阈值可配:允许用户自定义折叠的行数阈值
折叠标识:在折叠区域明确提示"展开查看详情",而不是完全消失
渐进式展开:先展示结论/要点,详情可点击展开

环境

Jcode 版本:v0.28.0
会话场景:项目架构分析、代码扫描、方案设计等长文本输出

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 locating the Jcode terminal interface that folds long AI replies, then reproduce the behavior with Markdown tables, code blocks, and replies around 30–40 lines on v0.28.0. Review the available rendering and configuration entry points before choosing among visible conclusions, a configurable threshold, or layered expansion. Done means long replies no longer hide their conclusion completely and the behavior is clear to the user.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
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.