Setting Up SuiteCloud Developer Assistant with Other Third-Party Tools and AI Coding Assistants

SuiteCloud CLI users can now securely connect to SuiteCloud Developer Assistant (SDA) using a dedicated command that activates a local proxy and enables seamless integration with third-party tools and AI coding assistants.

This integration gives you additional flexibility by allowing SDA to work with supported external tools and workflows, rather than only within a single environment. The setup lets you use SDA with IDEs or CLIs and AI coding assistants that support OpenAI-compatible providers, including WebStorm with Cline and Cline CLI.

For more information, see proxy:generatekey and proxy:start.

Note:

When you do operations that require NetSuite authentication, SuiteCloud SDK retrieves the passkey from secure storage and uses it to decrypt the credentials file. For this reason, ensure that secure storage is accessible and properly configured on your machine if you want to use browser-based authentication.

If secure storage isn't available, you can define a fallback passkey by creating the SUITECLOUD_FALLBACK_PASSKEY environment variable. This passkey must contain 32 to 100 alphanumeric characters. For information about how to set environment variables for different operating systems, see Setting Up Environment Variables for SuiteCloud SDK Tools.

Prerequisites

Before activating the local proxy, you must ensure that the following prerequisites are met:

Install and configure the latest version of SuiteCloud CLI. For more information, see SuiteCloud CLI for Node.js.
Ensure your account has SuiteCloud Developer Framework (SDF) enabled.
Authenticate using the appropriate NetSuite account. For more information, see account:setup.

To activate the local proxy and integrate with third-party tools:

During the initial SDA setup, generate an API key for proxy authentication by running suitecloud proxy:generatekey in a terminal. Store the key securely because you will need it later.

Note:
Generating a new API key replaces the previous key. After generating a new key, you must update the API key configuration in all third-party tools that use SDA.

For more information, see proxy:generatekey.
In the project directory, run suitecloud proxy:start to start the proxy and provide the required details: auth ID and port.

For more information, see proxy:start.
Depending on the tool you are using, do one of the following:
- If you are using an IDE extension (for example, and AI coding assistant installed as an extension in VS Code, WebStorm, or any other supported IDE), go to the provider settings and create a new custom provider. In this new custom provider, enter the required details: API provider, base URL, API key (previously generated), and model ID. For more information, see Using SuiteCloud Developer Assistant with Cline in WebStorm.
- If you are using a CLI (for example, an AI coding assistant that you run from the terminal), configure it with the required details: API provider, base URL, API key (previously generated), and model ID. For more information, see Using SuiteCloud Developer Assistant in Cline CLI.
In the IDE extension or the CLI of your choice, run a simple command or prompt to confirm that the flow works.

Note:

The following issues may indicate that the SDA API key is missing, invalid, corrupted, or could not be generated:

No SDA API key found.
Failed to start SDA proxy.
Error reading the Client API Key file contents.
The configured API key could not be validated.

To resolve these issues, generate a new API key by running the following command: suitecloud proxy:generatekey.

If the issue persists, delete the local Client API Key file and generate a new API key again. After generating a new key, update the API key in all configured third-party tools.

For more information, see Credentials and Passkey Errors.

Prerequisites

To activate the local proxy and integrate with third-party tools:

Related Topics