Skip to content

Support a --continue flag to persist context in a new session #1207

@mcncl

Description

@mcncl

Problem

Due to issues like #725, where limits aren't clear and no messaging is provided, it's easy to assume that OpenCode has just stopped working, so moving to another tool such as Amp or Claude Code is the assumed solution. However, those tools then inform you that limits have been reached. At that point though, context for OpenCode has been lost, so I need to interact with the tool to get it back up to speed with where we were.

Suggestion

Given we have a /share command, I would assume that there is some context stored for the current conversation. Would it be possible to therefore support a --continue flag when running opencode so that the previous conversation can continue and context is not lost? I would assume there are some logs or session information in the locally stored DB?

I appreciate that's a few assumptions, but I'd like to continue to use OpenCode and not have to quit out to check that usage limits are the issue, losing my progress and conversation.

Else, can we add information on usage limits to the conversation window?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions