[FEATURE]: Save conversations and session data to project folder

[TZubiri]

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

Data related to sessions is currently being saved to the ~/.opencode folder, even if working under another folder.

The suggestion is to save conversations to the folder of the project where opencode is ran.

This would help with #14291 yes.

But the main advantage would be that the conversations are the actual source code (using GPL definition of source code), and the code generated is actually target code. So saving the conversations allows users to more safely archive and save the source code of the applications they create, optionally adding them to source control if they wish to.

[R44VC0RP]

This is a good idea but going to close for now until we can consider this as an architectural decision in the future when it gets requested more.

[TZubiri]

That sounds reasonable. Would you be open to a transitional solution like:

A .opencode at a project root that consists only of soft links to the appropriate files in the root .opencode folder?

Might not be possible if the data is tied up in the sqlite database instead of split into clean files.

[thecove-tim]

@R44VC0RP where would "requested more" show up? I'll request here 😄

[neuronalism]

Requesting it too. I think this is an important feature that allows syncing the conversations for the same project across multiple devices.

[divohub]

Storing chat history inside the project directory would be much better. Sometimes a session opens in a different folder than the project, so it needs to be moved for file reading, access, and mentions to work correctly. I couldn't find a way to move the session history to another directory—it seems to be locked to the specific path. It looks like the only way is to manipulate the DB.

You can export a session to markdown with cmd+p Export Session or /export or you can from CLI run opencode export <session-id> which gives you a fuller json export.

Originally posted by @elijahmorg in #19017

As I mentioned, a workaround for now is to re-initialize the entire session using markdown or json export. Since the session history seems locked to the directory, exporting and then importing it into a new session in the correct path is probably the easiest way to keep things working properly without messing with the DB.

To open a session in the correct directory, first run opencode import <id session json or url>, then open the session with opencode -s <id session>.

[augusto-dmh]

What is being expected for this feature to be added? Honestly we need to have centered persistence of sessions and need to workaround this management that doesn't seem impossible to abstract.

[kirillp]

What is being expected for this feature to be added? Honestly we need to have centered persistence of sessions and need to workaround this management that doesn't seem impossible to abstract.

Usecase: I want to migrate project work to another pc, or switch beween pc`s quilcky. So storing all sessions data in .copencode allows me to git push this data and fetch on any other worstation or dev environment

[pejotigrek]

+1 on this! I work on couple of projects from different machines and now I have session history fragmented on all of them. it would be great to be able to keep it in one place, the project folder itself seems to be the best choice.