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

[FEATURE]: /continue command #3348

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

Originally created by @JosXa on GitHub (Dec 5, 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

It happens frequently that I need to interrupt the agent when I need to check that it isn't about to do something dangerous (giving myself a moment to read up), or opencode crashes and I need to restart. In these situations, I find myself typing "continue" in chat a lot to kick the task off again.

This is kinda annoying, produces unnecessary context, and isn't integrated as nicely as I'd like (e.g. it keeps the "command was interrupted" error in).

A /continue command for this purpose would be great. It could even delete the most recent incomplete message and have the AI start that last command or message from scratch again.

Originally created by @JosXa on GitHub (Dec 5, 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 It happens frequently that I need to interrupt the agent when I need to check that it isn't about to do something dangerous (giving myself a moment to read up), or opencode crashes and I need to restart. In these situations, I find myself typing "continue" in chat a lot to kick the task off again. This is kinda annoying, produces unnecessary context, and isn't integrated as nicely as I'd like (e.g. it keeps the "command was interrupted" error in). A /continue command for this purpose would be great. It could even delete the most recent incomplete message and have the AI start that last command or message from scratch again.
yindo added the discussion label 2026-02-16 17:39:43 -05:00
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #2404: headless mode --resume - Requests a --resume flag similar to Claude Code
  • #4801: Print some info when exiting: title, command to resume, usage stats - Requests better session resumption features
  • #4186: "revert message" should place reverted message in the prompt input - Related feature about recovering/continuing from previous actions

These issues all touch on resuming or continuing from where you left off. Feel free to ignore if your /continue command proposal addresses these in a different way.

@github-actions[bot] commented on GitHub (Dec 5, 2025): This issue might be a duplicate or closely related to existing issues. Please check: - #2404: headless mode --resume - Requests a `--resume` flag similar to Claude Code - #4801: Print some info when exiting: title, command to resume, usage stats - Requests better session resumption features - #4186: "revert message" should place reverted message in the prompt input - Related feature about recovering/continuing from previous actions These issues all touch on resuming or continuing from where you left off. Feel free to ignore if your `/continue` command proposal addresses these in a different way.
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Dec 5, 2025):

You can just type "Continue." or even make yourself a custom slash command for /continue. Doesn't seem like it really needs any changes in the code to do this... personally I just have a key on my keyboard that types "Continue.".

@ariane-emory commented on GitHub (Dec 5, 2025): You can just type "Continue." or even make yourself a custom slash command for `/continue`. Doesn't seem like it really needs any changes in the code to do this... personally I just have a key on my keyboard that types "Continue.".
yindo commented 2026-02-16 17:39:43 -05:00
Author
Owner
Copy Link
Copy Source

@JosXa commented on GitHub (Dec 6, 2025):

You can just type "Continue." or even make yourself a custom slash command for /continue. Doesn't seem like it really needs any changes in the code to do this... personally I just have a key on my keyboard that types "Continue.".

Sure, I get it. It does mess with the dialog though. When the agent was just going to send one more message and stop, now it will "continue" the original plan further.

@JosXa commented on GitHub (Dec 6, 2025): > You can just type "Continue." or even make yourself a custom slash command for `/continue`. Doesn't seem like it really needs any changes in the code to do this... personally I just have a key on my keyboard that types "Continue.". Sure, I get it. It does mess with the dialog though. When the agent was just going to send one more message and stop, now it will "continue" the original plan further.
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

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

u said it crashes? Never had that happen and very worrying unless you are a windows user because thatd be a bun bug out of our control

@rekram1-node commented on GitHub (Dec 6, 2025): u said it crashes? Never had that happen and very worrying unless you are a windows user because thatd be a bun bug out of our control
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

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

you want a built in slash command that just says “continue”?

@rekram1-node commented on GitHub (Dec 6, 2025): you want a built in slash command that just says “continue”?
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

@JosXa commented on GitHub (Dec 6, 2025):

Windows.
No, it shouldn't send the word "continue", it should prompt the LLM with that conversation again. Thinking about it now, that's possible, right? Like have the last message in the sent conversation be an assistant message and it will keep talking?

@JosXa commented on GitHub (Dec 6, 2025): Windows. No, it shouldn't _send_ the word "continue", it should prompt the LLM with that conversation again. Thinking about it now, that's possible, right? Like have the last message in the sent conversation be an assistant message and it will keep talking?
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

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

OH I see what you mean, is that the same as doing /undo and then reprompting? It seems somewhat similar..

@rekram1-node commented on GitHub (Dec 7, 2025): OH I see what you mean, is that the same as doing /undo and then reprompting? It seems somewhat similar..
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Dec 7, 2025):

@JosXa Okay, I get what you mean now, there might be advantages to the approach you're describing.

@ariane-emory commented on GitHub (Dec 7, 2025): @JosXa Okay, I get what you mean now, there might be advantages to the approach you're describing.
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

@JosXa commented on GitHub (Dec 7, 2025):

/undo and reprompting - sorta, but not quite. That will start with a user message. In Roo Code, you can arbitrarily stop and then continue the autonomous agent. No idea how they implement it.

Basically I'm asking for pause and resume

@JosXa commented on GitHub (Dec 7, 2025): /undo and reprompting - sorta, but not quite. That will start with a user message. In Roo Code, you can arbitrarily stop and then continue the autonomous agent. No idea how they implement it. Basically I'm asking for pause and resume
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

@JosXa commented on GitHub (Dec 7, 2025):

Thanks for the work @ariane-emory!!

@JosXa commented on GitHub (Dec 7, 2025): Thanks for the work @ariane-emory!!
yindo commented 2026-02-16 17:39:44 -05:00
Author
Owner
Copy Link
Copy Source

@ariane-emory commented on GitHub (Dec 7, 2025):

@JosXa Thanks! Haven't had the chance to properly test my experiment out yet, hopefully I'll get a chance to do so pretty soon.

@ariane-emory commented on GitHub (Dec 7, 2025): @JosXa Thanks! Haven't had the chance to properly test my experiment out yet, hopefully I'll get a chance to do so pretty soon.
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#3348
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?