update run configs

Author: Patrick-Erichsen

.vscode/launch.json

@@ -137,24 +137,5 @@
         "NODE_OPTIONS": "--experimental-vm-modules"
       }
     }
-    // {
-    //   "name": "[openai-adapters] Jest Test Debugger, Current Open File",
-    //   "type": "node",
-    //   "request": "launch",
-    //   "runtimeArgs": [
-    //     "--inspect-brk",
-    //     "${workspaceRoot}/packages/openai-adapters/node_modules/jest/bin/jest.js",
-    //     "--runInBand",
-    //     "--config",
-    //     "${workspaceRoot}/packages/openai-adapters/jest.config.mjs",
-    //     "${relativeFile}"
-    //   ],
-    //   "cwd": "${workspaceRoot}/packages/openai-adapters",
-    //   "console": "integratedTerminal",
-    //   "internalConsoleOptions": "neverOpen",
-    //   "env": {
-    //     "NODE_OPTIONS": "--experimental-vm-modules"
-    //   }
-    // }
   ]
 }

extensions/intellij/.run/Tail Dev Logs (core).run.xml

@@ -1,23 +1,24 @@
 # Contributing to Continue (JetBrains extension) <!-- omit in toc -->
 
-This file is for contribution guidelines specific to the JetBrains extension. See the root [`CONTRIBUTING.md`](../../CONTRIBUTING.md) for general contribution guidelines.
+This file is for contribution guidelines specific to the JetBrains extension. See the root [
+`CONTRIBUTING.md`](../../CONTRIBUTING.md) for general contribution guidelines.
 
 ## Table of Contents <!-- omit in toc -->
 
 - [Architecture Overview](#architecture-overview)
 - [Environment Setup](#environment-setup)
-  - [IDE Installation](#ide-installation)
-  - [IDE configuration](#ide-configuration)
-  - [Node.js Requirements](#nodejs-requirements)
-  - [Install all dependencies](#install-all-dependencies)
-  - [Misc](#misc)
+    - [IDE Installation](#ide-installation)
+    - [IDE configuration](#ide-configuration)
+    - [Node.js Requirements](#nodejs-requirements)
+    - [Install all dependencies](#install-all-dependencies)
+    - [Misc](#misc)
 - [Development Workflow](#development-workflow)
-  - [Running the extension](#running-the-extension)
-  - [Reloading changes](#reloading-changes)
-  - [Setting breakpoints](#setting-breakpoints)
-  - [Available Gradle tasks](#available-gradle-tasks)
-  - [Packaging](#packaging)
-    - [Testing the packaged extension](#testing-the-packaged-extension)
+    - [Running the extension](#running-the-extension)
+    - [Reloading changes](#reloading-changes)
+    - [Setting breakpoints](#setting-breakpoints)
+    - [Available Gradle tasks](#available-gradle-tasks)
+    - [Packaging](#packaging)
+        - [Testing the packaged extension](#testing-the-packaged-extension)
 
 ## Architecture Overview
 
@@ -57,36 +58,27 @@ This project requires Node.js version 20.11.0 (LTS) or higher. You have two opti
 
 ## Development Workflow
 
-Because the `gui` and `core` are written in TypeScript, our development workflow is built around the assumption that you
-have VS Code installed.
+### Running the extension in debug mode
 
-### Running the extension
+Select the "Run Continue" task in the top right corner of the IDE and then select the "Debug" option.
 
-- Open the project in VS Code and star the `Core binary` task
-- Switch back to Intellij and select the "Run Continue" configuration in the top-right corner of the IDE
-- Click the "Debug" button
-  - The first time running this will install the IDE version specified by the `platformVersion` property in [
-    `./run/Run Extension.run.xml`](./.run/Run%20Extension.run.xml). This will take a moment as the installation size
-    can be close to 1GB.
+![run-extension-screenshot](../../media/run-continue-intellij.png)
 
-![run-extension-screenshot](../../media/run-intellij-extension.png)\
-
-This should open a new instance on IntelliJ with the extension installed and connected via TCP to the server started
-through the `Core binary` task.
+This should open a new instance on IntelliJ with the extension installed.
 
 ### Reloading changes
 
 - `extensions/intellij`: Attempt to reload changed classes by selecting
   _Run | Debugging Actions | Reload Changed Classes`_
-  - This will often fail on new imports, schema changes etc. In that case, you need to stop and restart the extension
+    - This will often fail on new imports, schema changes etc. In that case, you need to stop and restart the extension
 - `gui`: Changes will be reloaded automatically
-- `core`: Run `npm run build` from the `binary` directory and restart the `Core binary` task in VS Code
+- `core`: Run `npm run build` from the `binary` directory (requires restarting the `Start Dev Server (core)` task)
 
 ### Setting breakpoints
 
 - `extensions/intellij`: Breakpoints can be set in Intellij
 - `gui`: You'll need to set explicit `debugger` statements in the source code, or through the browser dev tools
-- `core`: Breakpoints can be set in VS Code (requires restarting the _Core Binary_ task)
+- `core`: Breakpoints can be set in Intellij (requires restarting the `Start Dev Server (core)` task)
 
 ### Available Gradle tasks
 
@@ -111,7 +103,8 @@ verifyPluginConfiguration - Checks if Java and Kotlin compilers configuration me
 - Unix: `./gradlew buildPlugin`
 - Windows: `./gradlew.bat buildPlugin`
 
-This will generate a .zip file in `./build/distributions` with the version defined in [`./gradle.properties`](./gradle.properties)
+This will generate a .zip file in `./build/distributions` with the version defined in [
+`./gradle.properties`](./gradle.properties)
 
 #### Testing the packaged extension
 

extensions/intellij/CONTRIBUTING.md

@@ -36,7 +36,7 @@ function JetBrainsFetchGitHubTokenDialog({
   return (
     <div className="flex flex-col gap-3 p-8">
       <div className="text-center">
-        <h1 className="my-0 text-md">Sign in with GitHub</h1>
+        <h1 className="my-0 text-xl">Sign in with GitHub</h1>
         <p className="text-sm">
           Continue will request read access to your GitHub email so that we can
           prevent abuse of the free trial. If you prefer not to sign in, you can