The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

A local Apex runtime and debugger now runs inside IntelliJ IDEA (opens in a new tab)

You will learn how the renmy runtime JetBrains plugin runs Apex tests and debugs Apex locally in IntelliJ IDEA, what it needs, and how it fits alongside an org-based workflow and Illuminated Cloud.

Org-based workflow

  • Save and deploy to an org
  • Wait for the test to run
  • Download and read a debug log
  • No breakpoints to stop on

Local runtime workflow

  • Run icon beside each test
  • Tests run locally in under a second
  • Native debugger with breakpoints
  • Consoles run against local data
Apex work with and without a local runtime in IntelliJ IDEA

The JetBrains plugin formerly listed as “Nimbus - Local Apex Runtime” is now Renmy Runtime - Salesforce IDE, version 1.15.1, following the October 2026 rename of the underlying runtime to renmy runtime. The article presents it as a way to bring a local Apex runtime into IntelliJ IDEA Community or Ultimate. The runtime executes Apex, SOQL, DML and Salesforce Flows on the developer’s machine against an embedded PostgreSQL, without needing a Salesforce org, Scratch Org, Docker or a separate JVM. The author argues that Apex developers have never had the gutter run icons, breakpoints and local consoles that Java developers take for granted.

Setup is short. The plugin installs from the JetBrains Marketplace, and on first open of a project containing sfdx-project.json it installs its runtime into ~/.nimbus/bin. The Free tier needs no account. Each @IsTest class and method gets a run icon and Run, Debug, Coverage and Trace lenses, and results stream into IntelliJ’s test tree with time and SOQL and DML counts per method. The plugin uses the same backends as the CLI, so a test that passes in the IDE should pass under renmy test in a terminal or CI. Debugging uses a native session with breakpoints in .cls and .trigger files, and a replay mode that can step backwards through a recorded run. Recording is free, while stepping is Pro and free during the public beta. The article points to a public parity record and a benchmark, which reports 837 tests running in about 2.4 seconds locally against roughly 1 minute 46 seconds in an org.

The tool window groups features into six workspaces: Home, Develop, Org, Verify, Release and Admin. Develop holds Apex and SOQL consoles that can target the local runtime or any org the CLI is logged into, along with Run and Compare and Find in All Orgs. Org covers browsing, drift detection, debug-log replay and a Data Loader that simulates CSV loads locally and reports rejected rows before any upload. Editing adds sixteen inspections, refactorings, generators, live templates and metadata shown as forms. Previews render React, LWC and Visualforce, though only 25 of 77 Apex: components are drawn fully.

The plugin is described as working alongside Illuminated Cloud. Its shortcuts sit in the Alt+Shift namespace to avoid collisions, and a Tools → Renmy setting decides which Apex file types it keeps when Illuminated Cloud is installed. The article presents the local loop as complementing a sandbox rather than replacing it, with renmy deploy validating the same code in the org before deploying. The Free tier is $0 for one machine, while Pro is free during the beta and listed at $19 a month afterwards.

Read the original at dev.to (opens in a new tab)

Worth reading?

Master six overlooked Developer Console features to speed up debugging and querying (opens in a new tab)

You will learn how to configure saved workspace layouts, set persistent debug log levels, and use checkpoints and tree views to trace execution faster.

Why read this

The guide also explains how to export raw logs for side-by-side comparison when troubleshooting production issues.

The article positions the Developer Console as a lightweight scratchpad for quick queries and debugging, highlighting six underused capabilities that improve daily workflows. It begins by explaining how saved perspectives organize interface panels for specific tasks like data investigation versus breakpoint tracing.

It details how checkpoints capture heap and variable state at exact execution lines without cluttering code with debug statements. The author also recommends defining custom log levels for Execute Anonymous runs to filter out noise and speed up analysis.

Further tips cover the Query Editor, which now supports multi-line SOQL and maintains session history for rapid iteration. Debug logs can be navigated using a tree view to isolate specific classes, and the raw log export function allows developers to download and diff outputs across environments to pinpoint failures.

The piece concludes by reinforcing that while the console handles ad-hoc tasks efficiently, Visual Studio Code with the Salesforce extensions remains the superior choice for source tracking, testing, and deployment workflows.

Read the original at dev.to (opens in a new tab)

Worth reading?

Salesforce announces general availability of Web Console as a modern browser-based IDE (opens in a new tab)

Readers will learn how to access and use the new Web Console for inline Apex and Lightning Web Component editing, debugging, and query execution directly inside their org.

Why read this

The article explains the production guardrails, Setup steps, and how it differs from the legacy Developer Console and Agentforce Vibes IDE.

Salesforce has released Web Console as a generally available browser-based integrated development environment. Built on VS Code for the Web and the existing Salesforce extensions, it serves as a modern replacement for the legacy Developer Console while maintaining platform safety standards.

The tool supports core development tasks including inline editing of Apex classes and triggers, viewing and modifying Lightning Web Component files, running anonymous Apex scripts, and executing SOQL queries with optional Performance Plans. Developers can also run test suites, manage Trace Flags for debugging, and navigate the entire metadata tree using the Org Browser.

Access controls differ by environment, allowing read-only inspection in production orgs while permitting direct saves in sandboxes. Administrators can enable the feature through the Setup menu, where it is turned on by default. The announcement clarifies that this lightweight single-org editor targets quick troubleshooting and routine edits, distinct from the heavier virtual machine-backed Agentforce Vibes IDE.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?