Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: One Session over multiple VS Code Windows #55

Closed
tuefekci opened this issue Jan 15, 2023 · 6 comments
Closed

Feature Request: One Session over multiple VS Code Windows #55

tuefekci opened this issue Jan 15, 2023 · 6 comments

Comments

@tuefekci
Copy link

tuefekci commented Jan 15, 2023

Can we store the session information globally so that all VS Code windows have access to the same session?

EDIT: I looked into the code and it looks like it already uses the global state but for me if i open another window it still opens chrome again perhaps there is another issue somewhere?

@jonschlinkert
Copy link

Yes, for me as well. It opens a new window to authenticate every time I run any ChatGPT command.

@Trahloc
Copy link

Trahloc commented Feb 11, 2023

I'd like this feature as well please. I spent several hours working with one instance and it learned to do diff patch files which is quite handy. The new "new chat" iteration refuses to create diff patches so I have to wait for the whole code to repeat. I still have access to the old instance, which I've renamed "diff patcher", through the browser but I thought it'd be nice to reuse that inside vscode. Perhaps through use these instances become better at specific tasks? I was able to get another version familiar with recent file standard by pasting the source code into it (slowly to not overload the buffer). So the ability to reuse sessions would be really handy.

Thank you for your consideration.

@flutterrausch
Copy link

I'd like this feature as well please. I spent several hours working with one instance and it learned to do diff patch files which is quite handy. The new "new chat" iteration refuses to create diff patches so I have to wait for the whole code to repeat. I still have access to the old instance, which I've renamed "diff patcher", through the browser but I thought it'd be nice to reuse that inside vscode. Perhaps through use these instances become better at specific tasks? I was able to get another version familiar with recent file standard by pasting the source code into it (slowly to not overload the buffer). So the ability to reuse sessions would be really handy.

Thank you for your consideration.

Replaying an old (saved) conversation could be a useful workaround.

@gencay
Copy link
Owner

gencay commented Feb 27, 2023

@jonschlinkert @Trahloc @tuefekci @flutterrausch Hi everyone! I added conversation history support for browser autologin method. You can retrieve and continue the past conversations you had with ChatGPT.

With this on multiple vs-code instances you can access/continue different ChatGPT conversations.

It was hell of a work but I think it looks quite well within vs-code's such small sidebar. For now, you can only access the most recent 50 conversations. You can continue them, see their titles and creation times at the top of the window after opening a conversation. I'd appreciate if you could rate the extension on the marketplace for better visibility and adoption, this was a quite big feature to implement within limited time on a weekend ;)

Here's a sneak peek of how it works:
conversation-history

@gencay gencay closed this as completed Feb 27, 2023
@flutterrausch
Copy link

flutterrausch commented Feb 27, 2023

Wow, extremely cool, thanks a lot! ❤️

Some minor UI ideas, that I just had while trying the feature:

  • show a bit of preview for each entry ('new chat'..)
  • add a delete button for each entry

No need to implement :-)

@jonschlinkert
Copy link

@gencay thanks for the hard work, that's fantastic!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants