SuiteCloud Developer Assistant Now Exposes a Local Proxy for Third-Party AI Coding Assistants

What changed

SuiteCloud CLI now ships two new commands that stand up a local proxy server, exposing SuiteCloud Developer Assistant (SDA) as an OpenAI-compatible provider. Previously SDA was only usable inside the SuiteCloud Extension for VS Code; this proxy decouples it so any IDE extension or CLI that can talk to an OpenAI-compatible endpoint can consume SDA context.

New CLI commands

• suitecloud proxy:generatekey — generates a local API key used to authenticate requests to the proxy. Generating a new key invalidates the previous one, so every connected tool must be re-configured afterward.
• suitecloud proxy:start — starts the local proxy in the current SuiteCloud project directory. Requires an auth ID (from account:setup) and a port number.

Supported tools

Any tool that supports custom OpenAI-compatible providers can connect. Oracle specifically names:

• Cline extension in WebStorm (or VS Code)
• Cline CLI (terminal-based)

Configuration in the tool requires four values: API provider (custom/OpenAI-compatible), base URL (the local proxy URL, e.g. http://localhost:<port>), API key (from proxy:generatekey), and model ID (as exposed by SDA).

Authentication details

The proxy relies on SuiteCloud SDK’s existing credential chain. Credentials are decrypted at runtime using the passkey from your OS secure storage. If secure storage is unavailable (headless CI, containers, etc.), set the environment variable SUITECLOUD_FALLBACK_PASSKEY to a 32–100 character alphanumeric string.

Prerequisites

1. Latest SuiteCloud CLI for Node.js installed and on PATH.
2. SuiteCloud Development Framework (SDF) enabled on the target account.
3. A valid authentication profile created via suitecloud account:setup.

What to do

1. Update SuiteCloud CLI to the latest version: npm install -g @oracle/suitecloud-cli (verify the exact package name in Oracle’s docs; it may differ by distribution channel).
2. Run suitecloud proxy:generatekey once and store the returned key securely.
3. In your SuiteCloud project directory, run suitecloud proxy:start --authid <yourAuthId> --port <port>.
4. In your AI coding assistant (Cline, etc.), add a custom OpenAI-compatible provider pointing at http://localhost:<port> with the generated API key and the SDA model ID.
5. Send a test prompt to confirm the round-trip works.

Troubleshooting

If the proxy fails to start or the tool returns authentication errors, Oracle lists these common symptoms:

• 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

In each case, regenerate the key with suitecloud proxy:generatekey, update every connected tool, and retry. If the error persists, delete the local Client API Key file and regenerate.

Caveats

Oracle does not specify exactly which SDA model IDs are available through the proxy, nor whether governance or rate limits apply to proxy-routed requests. The release note also does not clarify whether the proxy can serve multiple concurrent tool connections on the same port. Confirm these details against the full SuiteCloud Developer Assistant Guide before rolling this into team workflows or CI pipelines.