Draft persistence: unsubmitted prompts are lost on focus change

未关闭
#1,087 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
cli

调研方向

The issue identifies the composer input and ~/.commandcode/history.jsonl, but gives no source files or tests. Start by locating where composer input is cleared on focus changes and how sessions are resumed. Done means unsubmitted text can be restored after a focus change or session resume, as described in the issue.

由索引模型根据 Issue 内容生成。

描述

Feature Description

Typing a long, situation-based prompt (40+ lines) in the composer is easy to
lose: an accidental click/refocus wiped the entire input with no way back.

Unsubmitted composer text lives only in memory. Confirmed there is no draft
file in ~/.commandcode and ~/.commandcode/history.jsonl only gains an entry on
submit, so there is nothing to recover from.

Request: persist the composer draft (e.g. debounced autosave to a per-session
draft file), and restore it when the input is re-focused or the session is
resumed. Even a "restore last discarded input" binding would be enough.

Workaround I'm using now: Ctrl+G to compose in $EDITOR.

Use Case

No response

Additional Context

No response

How important is this to you?

None

主要语言
没有语言数据
星标
4.2k
派生
377
平均合并
1 天 3 小时
30 天内合并 PR
6

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CommandCodeAI/command-code 的其他 Issue

查看 CommandCodeAI/command-code 的全部 Issue

相似的 Issue

更多 CLI Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。