Data is synced from the Chrome Web Store. View the official store page for the most current information.
If you are unable to retrieve a conversation, please reload and try again. Conversations that have been left unattended for a long time may not be retrieved. The principle is that if the session key obtained when the conversation begins is valid, it is used to retrieve the conversation log from the server. If the session becomes invalid, it will no longer be possible to retrieve it using that key. Also, it will not work if the cid UUID is not included in the URL. --- 会話が取得できないときは、リロードして試してください。長時間放置された会話は取得できない場合があります。原理は、会話を始めた時に得られるセッションキーが有効な場合において、それを利用し、サーバーから会話ログを取得します。セッションが無効となった場合、そのキーでは取得できなくなります。また URL に cid UUID が含まれない場合は機能しません。 --- The source code is publicly available, so please customize it and use it. ソースコードは公開されています。カスタマイズしてご利用ください。 https://github.com/Deskuma/chatgpt-chatlog-export
Hello, thought I should let you know that this isn't working - every conversation, whether in a project or not, returns json as: { "detail": { "message": "Conversation <redacted> not found.", "code": "conversation_not_found" } } I don't wanna sandbag you so I'll change my review score if this gets fixed!
It's useful when you want to quickly have the current conversation at hand as data. There's no hassle of the time lag involved in officially requesting an export and obtaining the archive. It's obtained as JSON data, so it can be converted into any type of data. It also includes conversation branching data. The data also includes the AI's thoughts. It does not include attached data. So it's very versatile.