anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Editing prompts in editor should include some conversation history #3275

New Issue
Open
opened 2026-02-16 17:39:28 -05:00 by yindo · 12 comments
yindo commented 2026-02-16 17:39:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @benceferdinandy-signifyd on GitHub (Dec 3, 2025).

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I recently noticed Claude has the AskUserQuestion tool which is an interactive picker with tabs and all. Looks something like this:

Image

Now I'm not sure this is the best solution, but it is true, that currently answering followup questions is quite the pain, since sometimes it can overflow the screen.

What would be pretty awesome, and probably useful for other things as well, if I could invoke the editor with the previous agent output quoted, instead of just what I have in the prompt, just like when I would be replying to an email in TUI. This would also be useful when I want to write something more complex, but I want the context of where we are (the editor takes over the entire screen so I'm left to remember).

How I imagine this is having a command like editor-reply, and assuming you already had something typed into the prompt it would open your EDITOR with

> This was the LLM output
> Question 1
> Question 2

My partial prompt is here

Answering question inline would be a breeze (and very familiar to people who write emails in a TUI editor).

Originally created by @benceferdinandy-signifyd on GitHub (Dec 3, 2025). ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request I recently noticed Claude has the `AskUserQuestion` tool which is an interactive picker with tabs and all. Looks something like this: <img width="1242" height="433" alt="Image" src="https://github.com/user-attachments/assets/0957f5a2-fe4e-4820-9aa2-2544283b0dc7" /> Now I'm not sure this is the best solution, but it is true, that currently answering followup questions is quite the pain, since sometimes it can overflow the screen. What would be pretty awesome, and probably useful for other things as well, if I could invoke the editor with the previous agent output quoted, instead of just what I have in the prompt, just like when I would be replying to an email in TUI. This would also be useful when I want to write something more complex, but I want the context of where we are (the editor takes over the entire screen so I'm left to remember). How I imagine this is having a command like editor-reply, and assuming you already had something typed into the prompt it would open your EDITOR with ``` > This was the LLM output > Question 1 > Question 2 My partial prompt is here ``` Answering question inline would be a breeze (and very familiar to people who write emails in a TUI editor).
yindo added the discussion label 2026-02-16 17:39:28 -05:00
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 3, 2025):

Testing if comments work

@github-actions[bot] commented on GitHub (Dec 3, 2025): Testing if comments work
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 3, 2025):

This issue might be a duplicate of or related to existing issues. Please check:

  • #3858: Requests ability to edit certain files in PLAN mode, mentions the problem where agents get out of control in EDIT mode - similar concern about editor UX and control flow
  • #1798: Feature request for "More"-like functionality in scrolling output - addresses the issue of content overflowing the screen, which is a key pain point mentioned in this issue
  • #3547: Small screen compatibility - addresses the problem where output overflows and becomes hard to navigate/read on smaller terminal sizes
  • #1098: Copy pasting large text makes scrolling impossible - related to screen space management when dealing with large amounts of text/context

Feel free to ignore if these don't address your specific request for showing LLM output context in the editor with quoted responses.

@github-actions[bot] commented on GitHub (Dec 3, 2025): This issue might be a duplicate of or related to existing issues. Please check: - #3858: Requests ability to edit certain files in PLAN mode, mentions the problem where agents get out of control in EDIT mode - similar concern about editor UX and control flow - #1798: Feature request for "More"-like functionality in scrolling output - addresses the issue of content overflowing the screen, which is a key pain point mentioned in this issue - #3547: Small screen compatibility - addresses the problem where output overflows and becomes hard to navigate/read on smaller terminal sizes - #1098: Copy pasting large text makes scrolling impossible - related to screen space management when dealing with large amounts of text/context Feel free to ignore if these don't address your specific request for showing LLM output context in the editor with quoted responses.
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 3, 2025):

Yeah we are going to add this to the plan mode

@rekram1-node commented on GitHub (Dec 3, 2025): Yeah we are going to add this to the plan mode
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 3, 2025):

Do you think we can put this under:
https://github.com/sst/opencode/issues/3844

@rekram1-node commented on GitHub (Dec 3, 2025): Do you think we can put this under: https://github.com/sst/opencode/issues/3844
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@benceferdinandy-signifyd commented on GitHub (Dec 3, 2025):

@rekram1-node I see that is for tracking the Claude Code style question, which is fine. What do you think about the quote-reply thing I mentioned? I can open a new issue for that or rename this one if that is better for you.

@benceferdinandy-signifyd commented on GitHub (Dec 3, 2025): @rekram1-node I see that is for tracking the Claude Code style question, which is fine. What do you think about the quote-reply thing I mentioned? I can open a new issue for that or rename this one if that is better for you.
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 3, 2025):

Yeah I think we could rename this one, I get what you're saying

We could have things commented out or something and then you can see the convo history

@rekram1-node commented on GitHub (Dec 3, 2025): Yeah I think we could rename this one, I get what you're saying We could have things commented out or something and then you can see the convo history
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@benceferdinandy-signifyd commented on GitHub (Dec 3, 2025):

Yeah I think we could rename this one, I get what you're saying

We could have things commented out or something and then you can see the convo history

Ack. Although I would definitely suggest using quote > instead of comment # .

@benceferdinandy-signifyd commented on GitHub (Dec 3, 2025): > Yeah I think we could rename this one, I get what you're saying > > We could have things commented out or something and then you can see the convo history Ack. Although I would definitely suggest using quote `> ` instead of comment `# `.
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 3, 2025):

Yeah I wasn't trying to suggest which variation > works for me, just wanted to communicate we need something that makes it clear that it's commented out

@rekram1-node commented on GitHub (Dec 3, 2025): Yeah I wasn't trying to suggest which variation `>` works for me, just wanted to communicate we need something that makes it clear that it's commented out
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@dbpolito commented on GitHub (Dec 15, 2025):

hey, just opened https://github.com/sst/opencode/pull/5563 with a different approach, let me know your thoughts

@dbpolito commented on GitHub (Dec 15, 2025): hey, just opened https://github.com/sst/opencode/pull/5563 with a different approach, let me know your thoughts
yindo commented 2026-02-16 17:39:28 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 15, 2025):

@dbpolito Im not sure that pr is relevant to this discussion unless I misunderstood?

@rekram1-node commented on GitHub (Dec 15, 2025): @dbpolito Im not sure that pr is relevant to this discussion unless I misunderstood?
yindo commented 2026-02-16 17:39:29 -05:00
Author
Owner
Copy Link
Copy Source

@dbpolito commented on GitHub (Dec 15, 2025):

hmm, maybe not... i saw the mention of AskUserQuestion and thought it was more related to that feature... nvm then

@dbpolito commented on GitHub (Dec 15, 2025): hmm, maybe not... i saw the mention of `AskUserQuestion` and thought it was more related to that feature... nvm then
yindo commented 2026-02-16 17:39:29 -05:00
Author
Owner
Copy Link
Copy Source

@benceferdinandy-signifyd commented on GitHub (Jan 26, 2026):

@rekram1-node I still often run into the situation where the a) the question tool is not used and b) where it would make sense for me to have the original output available in the editor without me having to manually select it with the mouse. I still often find myself doing "select with mouse, open prompt in editor, paste selection"

@benceferdinandy-signifyd commented on GitHub (Jan 26, 2026): @rekram1-node I still often run into the situation where the a) the question tool is not used and b) where it would make sense for me to have the original output available in the editor without me having to manually select it with the mouse. I still often find myself doing "select with mouse, open prompt in editor, paste selection"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3275
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?