diff --git a/doc/development/code_suggestions/index.md b/doc/development/code_suggestions/index.md
index baed2c152b71783c2713cb76e67b5e7f913dad98..5f27e94a5eceec828b3b45c89b224f438f9dba31 100644
--- a/doc/development/code_suggestions/index.md
+++ b/doc/development/code_suggestions/index.md
@@ -11,34 +11,42 @@ info: Any user with at least the Maintainer role can merge updates to this conte
 The recommended setup for locally developing and debugging Code Suggestions is to have all 3 different components running:
 
 - IDE Extension (e.g. VS Code Extension)
-- Main application configured correctly
+- Main application configured correctly (e.g. GDK)
 - [AI Gateway](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist)
 
 This should enable everyone to see locally any change in an IDE being sent to the main application transformed to a prompt which is then sent to the respective model.
 
 ### Setup instructions
 
-1. Install and run locally the [VSCode Extension](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/CONTRIBUTING.md#configuring-development-environment)
-   1. Add the ```"gitlab.debug": true,``` info to the Code Suggestions development config
+1. Install and run locally the [VSCode Extension](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/CONTRIBUTING.md#configuring-development-environment):
+   1. Add the ```"gitlab.debug": true,``` info to the Code Suggestions development config:
       1. In VS Code navigate to the Extensions page and find "GitLab Workflow" in the list
       1. Open the extension settings by clicking a small cog icon and select "Extension Settings" option
       1. Check a "GitLab: Debug" checkbox.
+   1. If you'd like to test code suggestions are working from inside the VS Code Extension, then follow the [steps to setup a personal access token](https://gitlab.com/gitlab-org/gitlab-vscode-extension/#setup) with your GDK inside the new window of VS Code that pops up when you run the "Run and Debug" command
+      - Once you complete the steps below, to test you are hitting your local `/code_suggestions/completions` endpoint and not production, follow these steps:
+         1. Inside the new window, in the built in terminal select the "Output" tab then "GitLab Language Server" from the drop down menu on the right
+         1. Open a new file inside of this VS Code window and begin typing to see code suggestions in action
+         1. You will see completion request URLs being fetched that match the Git remote URL for your GDK
 1. Main Application (GDK):
    1. Install the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/index.md#one-line-installation).
-   1. Enable Feature Flag ```code_suggestions_tokens_api```
+   1. Enable Feature Flag ```code_suggestions_tokens_api```:
       1. In your terminal, navigate to your `gitlab-development-kit` > `gitlab` directory.
       1. Run `gdk rails console` or `bundle exec rails c` to start a Rails console.
-      1. [Enable the Feature Flag](../../administration/feature_flags.md#enable-or-disable-the-feature) for the code suggestions tokens API by calling 
+      1. [Enable the Feature Flag](../../administration/feature_flags.md#enable-or-disable-the-feature) for the code suggestions tokens API by calling
          `Feature.enable(:code_suggestions_tokens_api)` from the console.
-   1. Run the GDK with ```export AI_GATEWAY_URL=http://localhost:5052```
+   1. Set the AI Gateway URL environmental variable by running ```export AI_GATEWAY_URL=http://localhost:5052```
+   1. Run your GDK server with `gdk start` if it's not already running
 1. [Setup AI Gateway](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist):
     1. Complete the steps to [run the server locally](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist#how-to-run-the-server-locally).
         - If running `asdf install` doesn't install the dependencies in ``.tool-versions``, you may need to run `asdf plugin add <name>` for each dependency first.
     1. Inside ``poetry shell``, build tree sitter libraries by running ```poetry run scripts/build-tree-sitter-lib.py```
-    1. Add the following variables to the `.env` file for all debugging insights:
-        1. `AIGW_LOGGING__LEVEL=DEBUG`
+    1. Uncomment or add the following variables in the `.env` file for all debugging insights:
+        1. `AIGW_LOGGING__LEVEL=debug`
         1. `AIGW_LOGGING__FORMAT_JSON=false`
-        1. `AIGW_LOGGING__TO_FILE=true`
+        1. `AIGW_LOGGING__TO_FILE=../modelgateway_debug.log`
+            1. Note you may need to adjust the filepath (remove `..`) for this log to show in the `ai-assist` root directory
+        1. If you run into an error with `tree-sitter`, you may also need to explicitly define the path to the `lib` directory by adding something like `LIB_DIR=/Users/username/src/ai-assist/scripts/lib`
     1. Watch the new log file ```modelgateway_debug.log``` , e.g. ```tail -f modelgateway_debug.log | fblog -a prefix -a suffix -a current_file_name -a suggestion -a language -a input -a parameters -a score -a exception```
 
 ### Setup instructions to use staging AI Gateway
@@ -46,7 +54,7 @@ This should enable everyone to see locally any change in an IDE being sent to th
 When testing interactions with the AI Gateway, you might want to integrate your local GDK
 with the deployed staging AI Gateway. To do this:
 
-1. You need a [cloud staging license](../../user/project/repository/code_suggestions/self_managed_prior_versions.md#upgrade-to-gitlab-163) that has the Code Suggestions add-on, because add-ons are enabled on staging. Drop a note in the `#s_fulfillment` internal Slack channel to request an add-on to your license. See this [handbook page](https://handbook.gitlab.com/handbook/developer-onboarding/#working-on-gitlab-ee-developer-licenses) for how to request a license for local development.
+1. You need a [cloud staging license](../../user/project/repository/code_suggestions/self_managed_prior_versions.md#upgrade-to-gitlab-163) that has the Code Suggestions add-on, because add-ons are enabled on staging. Drop a note in the `#s_fulfillment` or `s_fulfillment_engineering` internal Slack channel to request an add-on to your license. See this [handbook page](https://handbook.gitlab.com/handbook/developer-onboarding/#working-on-gitlab-ee-developer-licenses) for how to request a license for local development.
 1. Set environment variables to point customers-dot to staging, and the AI Gateway to staging:
 
    ```shell
@@ -58,3 +66,24 @@ with the deployed staging AI Gateway. To do this:
 1. Restart the GDK.
 1. Ensure you followed the necessary [steps to enable the Code Suggestions feature](../../user/project/repository/code_suggestions/self_managed.md).
 1. Test out the Code Suggestions feature by opening the Web IDE for a project.
+
+### Setup instructions to use GDK with the Code Suggestions Add-on
+
+On February 15, 2023 we will require the code suggestions add-on subscription to be able to use code suggestions.
+To setup your GDK for local development using the add-on, please follow these steps:
+
+1. Drop a note in the `#s_fulfillment` or `s_fulfillment_engineering` internal Slack channel to request an activation code with the Code Suggestions add-on
+1. Someone will reach out to you with a code
+1. Follow the [activation instructions](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/main/doc/license/cloud_license.md?ref_type=heads#testing-activation):
+   1. Set environment variables:
+
+   ```shell
+   export GITLAB_LICENSE_MODE=test
+   export CUSTOMER_PORTAL_URL=https://customers.staging.gitlab.com
+   export GITLAB_SIMULATE_SAAS=0
+   ```
+
+   1. Restart your GDK
+   1. Navigate to `/admin/subscription`
+   1. Remove any active license
+   1. Add the new activation code