SuiteCloud SDK 2026.1: Developer Assistant Lands Early, Rest of Toolchain Delayed to February

For 2026.1, the only SuiteCloud SDK component actually shipping on the release boundary is a new SuiteCloud Developer Assistant for Visual Studio Code. Every other piece of the SDK toolchain — the VS Code extension itself (full 2026.1 build), the Node.js CLI, the WebStorm plug-in, and the Java CLI — is deferred to February 2026. If you maintain CI/CD that depends on any of these, plan accordingly.

What changed

SuiteCloud Developer Assistant (new)

An AI coding assistant aimed specifically at SDF/SuiteScript work. It is delivered as a feature of the SuiteCloud Extension for VS Code, but it ships before the full 2026.1 extension and is wired through the third-party Cline VS Code extension rather than running natively in the SuiteCloud extension's own UI.

Capabilities Oracle calls out:

• Context-aware coding help inside an open SuiteCloud project
• Generation of SuiteScript 2.1 code from natural-language input (note: 2.1 specifically — not 2.0)
• Generation and management of XML custom objects (i.e., SDF object XML under src/Objects/)
• Per-task approval gating before the assistant writes to disk

The release notes do not specify which language model is used, where prompts/code are sent, what telemetry is collected, or how authentication to NetSuite is brokered through Cline. Verify all of this with your security team before enabling it on a production-connected workstation — see Oracle's SuiteCloud Developer Assistant Guide and Setting Up SuiteCloud Developer Assistant Using Cline for the actual details.

2026.1 SuiteCloud Extension for VS Code — delayed

The full 2026.1 build of the extension (the SDF UI layer) is targeted for February 2026. Until then, you will be on the late-2025.x extension plus the Developer Assistant preview. The extension remains open source on GitHub.

2026.1 SuiteCloud CLI for Node.js — delayed

The interactive Node-based CLI (suitecloud) used by most modern SDF pipelines is also targeted for February 2026. Any npm install -g @oracle/suitecloud-cli upgrade plans tied to the 2026.1 release date should be pushed back. Existing 2025.x CLI versions continue to work against 2026.1 accounts in the meantime, but new 2026.1-only project/object types may not validate until you upgrade.

2026.1 SuiteCloud IDE Plug-in for WebStorm — delayed

Same story: February 2026 target. JetBrains users stay on the prior plug-in build.

2026.1 SuiteCloud CLI for Java — delayed

The Java CLI — the one most teams wire into Jenkins/GitLab/Azure DevOps shell jobs for project:validate and project:deploy automation — is also delayed to February 2026. If your build agents pin a specific CLI version, do not bump to 2026.1 yet; it does not exist.

What's vague in the source

Oracle's note is unusually thin. It does not say:

• Which LLM provider powers the Developer Assistant, or whether prompts/code leave your machine
• Whether the Assistant respects existing project.json / manifest.xml dependency declarations when generating objects
• Whether generated SuiteScript 2.1 is validated against the JSDoc type definitions shipped with the extension
• Exact version numbers for any of the delayed components
• Whether the February 2026 slip affects the SDF server-side schema or only the client tooling (assume client only unless told otherwise)

Confirm each of these against the linked Oracle guides before rolling the Assistant out to a team.

What to do

1. Freeze your SDK versions. Pin @oracle/suitecloud-cli, the Java CLI JAR, and the VS Code / WebStorm extensions to your current 2025.x builds in CI. Do not chase a 2026.1 tag that does not exist yet.
2. Push the upgrade window to February 2026 or later. Re-test the full deploy pipeline (project:validate, project:deploy, object:import, file:import) once the real 2026.1 builds drop.
3. If you want to try the Developer Assistant: install it on a developer workstation only, not a build agent. Install the Cline VS Code extension as a prerequisite, then the SuiteCloud Extension for VS Code preview build. Keep it pointed at a sandbox account with a token-based role that has the minimum SDF permissions required.
4. Review with security/compliance first. Because code generation runs through Cline and an external LLM, treat any repo containing customer data, PII, or proprietary SuiteScript as in-scope for your AI-tooling policy before enabling the Assistant.
5. Force SuiteScript 2.1 in new work. The Assistant generates 2.1 only. If your shop is still standardizing on 2.0, decide now whether Assistant-generated code is allowed in PRs or must be ported.
6. Gate Assistant edits. Leave the per-task approval prompt enabled — do not auto-accept. Treat its output like a junior dev's PR: review every diff, especially anything touching deploy.xml, manifest.xml, or role/permission XML.
7. Watch the GitHub repos for the VS Code extension and the Node CLI for the actual 2026.1 tags in February rather than relying on the Help Center's release date.

Bottom line

2026.1 is, for SDK purposes, an AI-assistant preview release. The actual tooling refresh is a February 2026 event. Don't rewrite your build pipelines yet; do start your security review of the Developer Assistant now if you intend to adopt it.