Is the src folder out of date to the current release version in marketplace?

[ppipada]

I am trying to do some tweaks to the extension (have this https://github.com/gencay/vscode-chatgpt/discussions/67 question too). Looks like the OpenAI API support is present in the released vscode extension but not in the source code of this repo. Most probably same with package.json too. is this correct? Am I missing something?

[ncesar]

Are you looking into this release? https://github.com/gencay/vscode-chatgpt/releases/tag/v3.0.0

specically this tag: https://github.com/gencay/vscode-chatgpt/tree/v3.0.0

edit---

After looking into the current source code I was not able to find any relevant code related to OpenAI keys. Is there something we are missing @gencay ?

[ppipada]

Looking at main branch actually. Even after tracking back upto 3.0 it is same. For eg: package.json in current main is:

"configuration": {
      "title": "ChatGPT",
      "properties": {
        "chatgpt.promptPrefix.addTests": {
          "type": "string",
          "default": "Implement tests for the following code",
          "description": "The prompt prefix used for adding tests for the selected code"
        },
        "chatgpt.promptPrefix.findProblems": {
          "type": "string",
          "default": "Find problems with the following code",
          "description": "The prompt prefix used for finding problems for the selected code"
        },
        "chatgpt.promptPrefix.optimize": {
          "type": "string",
          "default": "Optimize the following code",
          "description": "The prompt prefix used for optimizing the selected code"
        },
        "chatgpt.promptPrefix.explain": {
          "type": "string",
          "default": "Explain the following code",
          "description": "The prompt prefix used for explaining the selected code"
        },
        "chatgpt.response.showNotification": {
          "type": "boolean",
          "default": false,
          "description": "Choose whether you'd like to receive a notification when ChatGPT bot responds to your query."
        }
      }

No GPT3 properties.

[gencay]

@ppipada @ncesar thanks for the engagement here folks. I am keeping the source code in my private repository at the moment due to various reasons (I explained it on this issue as well #37) To reiterate, after my initial implementation I saw various clones without respecting the license of this project, for which I am putting so much effort during my free-time for the community to utilize chatgpt in vs-code for free and all of a sudden vs-code marketplace was full of copy-pastes of my implementation/design. My plan is to update this public repository for browser-based autologin flow once it cools down and I've got enough features to carry on on this project with the help of the community. I believe in the power of open-source and I promise the source code will be live at some point, but I can't say when just yet.

I try to respond to feature requests/issues in my best ability here and address them in the extension as fast as possible.

I hope that addresses your question here. I will separately respond to your questions on your other issue #67 @ppipada.

[ppipada]

Thank you for your response @gencay. Thanks for your awesome work.

[ncesar]

Makes senses @gencay , I feel you. Let me know if there is something I can assist with your private repo. I do have JS experience but not with VScode, yet.

[songkeys]

I totally respect your and work choice but this should be noted in the README to avoid further confusion and misunderstanding. The produced extension being not actually the same as what the source code builds is very dangerous for an app asking for passwords and API keys.

[gencay]

@Songkeys thank you, I updated the Readme.md -> Disclaimers section. I understand your concern, however I think it's obvious, but I should still note that, this extension is purely running on your vs-code client without any server-side code that could intervene with your prompts, settings etc. There is a telemetry reporter that uses the vs-codes default instrumentation flow, so you can also opt-out if you prefer not to send anything to application insights (This is also noted in the disclaimer). Btw I also wanted the extension to warn the user not to store PII (Password/API Key/Email etc.) in settings.json and instead use the in-memory option for remembering the API Keys. Since you may be sharing your vs-code/computer with somebody else and they may see those settings in plain text, which is not secure. I should also note that you don't have to provide email/password to use the browser autologin method, you could just enter all of that information manually on the browser. Since the browser will open in a fresh/incognito window, I added those options to reduce the friction with using the extension so that you don't always have to manually enter, still you could do that though.

This is a hobby project without any monetary expectation but since I put so much of my time in here, I think it deserves the respect of not stealing/copy pasting code elsewhere, check out marketplace it's full of clones, I even saw an extension that copied the whole repository without changing a single code/readme and released it on marketplace :/. Once it's calmer out there about the ChatGPT, the code will be out in open source for sure, since I think it's where it belongs to! 🙏

[Christopher-Hayes]

I can attest, when I was first using this extension months back, there were already clones copy-pasting the repo without attribution.

I'd normally be a little sus about a non-paid project going private, but remembering that and Ali working on this basically non-stop for months, it's understandable.