Salesforce Org Nexus

Salesforce Org Nexus is an integrated Visual Studio Code workspace for Salesforce development, inspection and org operations. It brings metadata exploration, dependency analysis, REST and Bulk APIs, HTTP callout inspection, Platform Events, Apex/SOQL scripts, Org Health and the ORBIT AI assistant into one consistent interface.

Nexus follows the Salesforce org active in the current Salesforce DX project, so every workspace stays aligned with the org you are working on.

Nexus Command Hub

The Hub provides direct access to the main Nexus workspaces:

• Metadata
• REST
• Inspector
• Events
• Scripts
• Org Health
• ORBIT

The active Salesforce org and API version remain visible while moving between workspaces.

Metadata

The Metadata workspace provides three complementary ways to work with the active Salesforce org:

• Explorer — browse metadata by category, search types and components, select metadata, generate package.xml and retrieve into the current Salesforce DX project.
• Tree — navigate indexed metadata and relationships through a folder-style hierarchy.
• Dependency Graph — explore Depends on and Used by relationships in an interactive graph with search, filters, configurable depth and draggable nodes.

Nexus supports dependency analysis across important Salesforce metadata families, including Apex, Flow, objects and fields, Lightning components, validation rules, record types, permissions, Custom Metadata, Custom Settings, labels, Platform Events and other supported metadata.

The dependency index can be rebuilt on demand and Nexus exposes scan duration and Salesforce API usage to help evaluate large-org operations.

REST Explorer

REST Explorer provides a Salesforce API workspace with:

• GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS.
• API Navigator for standard REST resources, sObjects, SOQL, Composite APIs, Tooling API, UI API, GraphQL, Connect REST, Reports, Bulk APIs, Apex REST and custom endpoints.
• Request headers and body editing.
• Request history.
• Response status, timing, headers and payload size.
• Complete Salesforce error payloads when available.

Bulk operations

Dedicated workflows are available for:

• Bulk API 2.0 Ingest
• Bulk API 2.0 Query
• Bulk API 1.0

Nexus can guide and manage job creation, CSV upload, job closing, polling, result retrieval and formatted result inspection.

Bulk Query supports Query / Query All, configurable delimiters and result page sizes, full result pagination and CSV download.

Universal Response Viewer

Responses are displayed according to their content:

• JSON — structured expandable tree.
• CSV — tabular viewer.
• XML — formatted source.
• HTML — source-oriented rendering.
• Text — monospaced text viewer.
• Raw — original response view.

HTTP Callout Inspector

Inspector helps inspect outbound Salesforce HTTP traffic through a configured Nexus Relay.

It provides:

• explicit Start / Stop listening sessions;
• live inbound request capture;
• request overview, headers, body, structured JSON and raw payload inspection;
• search within the captured request;
• collapsible Request Headers and Request Body sections in the Overview;
• configurable HTTP response status, content type and response body returned to Salesforce;
• connection information required to route the Salesforce callout to the active Inspector session.

A compatible Relay can be hosted on the infrastructure selected by the user or organization. Inspector is not tied to a specific cloud provider.

Platform Events

The Events workspace can:

• discover Platform Events available in the active org;
• subscribe to events from Salesforce;
• inspect received payloads and Replay IDs;
• use new-events, resume and earliest-retained replay modes;
• publish test Platform Events using fields discovered from Salesforce metadata.

Platform Event listening is independent from HTTP Callout Inspector.

Scripts

The Scripts workspace manages Salesforce development scripts inside the current project:

• create and edit Anonymous Apex scripts;
• create and edit SOQL scripts;
• execute .apex against the active org;
• execute .soql and inspect query results;
• inspect execution history and saved output;
• open the configured Salesforce debug-log folder.

Org Health

Org Health provides an operational dashboard for the active Salesforce org.

It brings together Salesforce limits and operational metrics such as:

• Daily API usage and remaining requests.
• Platform Event capacity where exposed by the org.
• Org-wide Apex code coverage.
• Async Apex usage and recent job status.
• Data Storage and File Storage.
• Bulk, Streaming, Flow, Email, Analytics, Content, External Services and other limits returned by Salesforce.
• Searchable All Salesforce Limits catalog.

The dashboard highlights areas under pressure and makes the most relevant capacity information easier to inspect.

ORBIT

ORBIT is the optional AI assistant integrated into Nexus.

ORBIT can use context from the currently active Nexus workspace to help with tasks such as:

• explaining metadata and dependencies;
• analyzing REST and Bulk responses;
• preparing API requests;
• troubleshooting Salesforce errors;
• working with Apex and SOQL scripts;
• understanding Org Health information.

Supported integrations include Gemini, ChatGPT/OpenAI and aXet Gaia when the corresponding provider tooling is available in the local environment.

Actions that can change the Nexus workspace are presented for review and require explicit confirmation. ORBIT does not automatically execute Apex, send REST requests, start Bulk jobs, publish Platform Events or deploy metadata without a user action.

Activation and access

The official distributed build requires a valid Nexus activation for an authorized installation.

Activation is separate from the Salesforce connection used by the project. Salesforce access tokens, refresh tokens and session IDs are not required for Nexus activation.

Access can be expired or revoked independently from the Salesforce org connection.

Requirements

• Visual Studio Code 1.90.0 or later.
• Salesforce CLI (sf).
• Official Salesforce Extension Pack.
• A Salesforce DX project with an authorized target org.
• A valid Nexus activation for the official distributed build.
• A compatible Nexus Relay endpoint only when using HTTP Callout Inspector.
• A supported AI provider integration only when using the corresponding ORBIT provider.

Data handling and privacy

Nexus is designed so that Salesforce credentials remain associated with the user's local Salesforce connection rather than being reused as Nexus activation credentials.

At a functional level:

• Salesforce org access uses the active Salesforce CLI / VS Code connection selected for the project.
• Activation is used to authorize the Nexus installation and does not require Salesforce access tokens, refresh tokens or session IDs.
• HTTP Callout Inspector uses the configured Relay only for the traffic intentionally routed to an Inspector session.
• ORBIT sends context to the selected AI provider only when the user submits an ORBIT request. Provider-side processing and retention are governed by the selected provider.
• Local workspace operations such as project files, retrieved metadata, scripts and downloaded results remain part of the user's local VS Code workspace unless the user explicitly sends or exports them elsewhere.

License and third-party components

Salesforce Org Nexus is proprietary software. A valid activation grants the authorized user the right to install and use Nexus under the terms of LICENSE.txt. Copying, reproduction, redistribution, modification, repackaging, sublicensing and reverse engineering are prohibited except where applicable law provides a mandatory right that cannot be restricted.

Third-party components bundled with Nexus retain their own licenses. See THIRD_PARTY_NOTICES.txt for details.

Copyright © 2026 Francesco Rondinella. All rights reserved.