Code Suggestions development guidelines

Code Suggestions development setup

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 (e.g. GDK).
  • AI Gateway.

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 VS Code Extension:
    1. Add the "gitlab.debug": true info to the Code Suggestions development config:
      1. In VS Code, go to the Extensions page and find “GitLab Workflow” in the list.
      2. Open the extension settings by clicking a small cog icon and select “Extension Settings” option.
      3. Check a “GitLab: Debug” checkbox.
    2. If you’d like to test that Code Suggestions is working from inside the VS Code Extension, then follow the steps to set up a personal access token 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.
        2. Open a new file inside of this VS Code window and begin typing to see Code Suggestions in action.
        3. You will see completion request URLs being fetched that match the Git remote URL for your GDK.
  2. Main Application (GDK):
    1. Install the GitLab Development Kit.
    2. Enable Feature Flag ai_duo_code_suggestions_switch:
      1. In your terminal, go to your gitlab-development-kit > gitlab directory.
      2. Run gdk rails console or bundle exec rails c to start a Rails console.
      3. Enable the Feature Flag for the Code Suggestions tokens API by calling Feature.enable(:ai_duo_code_suggestions_switch) from the console.
    3. Setup AI Gateway.
    4. Run your GDK server with gdk start if it’s not already running.

Setup instructions to use staging AI Gateway

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 that has the Code Suggestions add-on, because add-ons are enabled on staging. Follow these instructions to add the add-on to your license (you can reach out to #s_fulfillment_engineering if you have any problems). See this handbook page for how to request a license for local development.

  2. Set environment variables to point customers-dot to staging, and the AI Gateway to staging: 

    export GITLAB_LICENSE_MODE=test
export CUSTOMER_PORTAL_URL=https://customers.staging.gitlab.com
export AI_GATEWAY_URL=https://cloud.staging.gitlab.com/ai
  3. Restart the GDK.
  4. Ensure you followed the necessary steps to enable the Code Suggestions feature.
  5. 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

  1. Add a GitLab Ultimate Self-Managed subscription with a Duo Pro subscription add-on to your GDK instance.

    1. Sign in to the staging Customers Portal by selecting the Continue with GitLab.com account button. If you do not have an existing account, you are prompted to create one.
    2. If you do not have an existing cloud activation code, visit the Ultimate Self-Managed Subscription page using the buy subscription flow link.
    3. Purchase the subscription using a test credit card.
    4. Once you have a subscription, on the subscription card, select the ellipse menu … > Buy Duo Pro add-on.
    5. Use the previously saved credit card information, and the same number of seats as in the subscription.

    After this step is complete, you will have an activation code for a GitLab Ultimate Self-Managed subscription with a Duo Pro add-on.

  2. Follow the activation instructions:

    1. Set environment variables. 

      export GITLAB_LICENSE_MODE=test
export CUSTOMER_PORTAL_URL=https://customers.staging.gitlab.com
export GITLAB_SIMULATE_SAAS=0

    On a non-GDK instance, you can set the variables using gitlab_rails['env'] in the gitlab.rb file: 

       gitlab_rails['env'] = {
   'GITLAB_LICENSE_MODE' => 'test',
   'CUSTOMER_PORTAL_URL' => 'https://customers.staging.gitlab.com',
   'AI_GATEWAY_URL' => 'https://cloud.staging.gitlab.com/ai'
   }
    1. Restart your GDK.
    2. Go to /admin/subscription.
    3. Optional. Remove any active license.
    4. Add the new activation code.
  3. Inside your GDK, navigate to Admin area > GitLab Duo Pro, go to /admin/code_suggestions
  4. Filter users to find root and click the toggle to assign a GitLab Duo Pro add-on seat to the root user

Setup instructions to use the Duo Pro add-on with a staging GitLab.com account

  1. Have your account ready at https://staging.gitlab.com
  2. Create a new group or use an existing one as the namespace which will receive the Duo Pro access
  3. Navigate to Settings > Billing
  4. Initiate the purchase flow for the Ultimate plan by clicking on Upgrade to Ultimate
  5. After being redirected to https://customers.staging.gitlab.com, click on Continue with your Gitlab.com account
  6. Purchase the SaaS Ultimate subscription using a test credit card
  7. Find the newly purchased subscription card, and select from the three dots menu the option Buy GitLab Duo Pro
  8. Purchase the GitLab Duo Pro add-on using the same test credit card from the above steps
  9. Go back to https://staging.gitlab.com and verify that your group has access to Duo Pro by navigating to Settings > GitLab Duo and managing seats