A modern browser-based IDE is now in beta — built for debugging, SOQL, and quick fixes without ever leaving Salesforce
If you've been waiting for Salesforce to replace the old Developer Console with something that doesn't feel like it was built in 2010, that day is here. Web Console opened its beta on April 14, 2026 — a browser-based IDE embedded directly into Salesforce that lets you debug, run SOQL, execute Anonymous Apex, and make quick code edits without leaving the platform.
What Is Web Console?
According to the official Salesforce Developer Blog post, Web Console is a browser-based IDE that lives directly inside Salesforce, designed to launch from places developers are already working — like Setup and other context-rich surfaces. The core idea Salesforce describes is simple: developers should not have to leave Salesforce to build Salesforce apps. They call it "code where you build."
This is more than just a new editor in a browser tab. Unlike the old Developer Console, Web Console is designed to launch from the issue itself — so you start from the problem, not from a file tree.
What's Included in the Beta
The official blog describes the beta as intentionally focused on the workflows developers use most when investigating and fixing something quickly. Here's what's in it:
| Feature | What it does |
|---|---|
| Debug Log Viewing | Inspect runtime behaviour with a dedicated logs experience — directly in the browser |
| SOQL Execution | Run queries and see results without switching to a separate tool |
| Query Plan Inspector | Understand query performance inline — no manual explain plan steps |
| Anonymous Apex | Execute Anonymous Apex without leaving the browser |
| Quick Apex Edits | Open Apex from Salesforce surfaces and make focused inline edits in context |
| Org-aware Metadata Navigation | Browse metadata without switching to a separate development environment |
Why It Feels Different: The Context Problem
The Salesforce blog post makes an honest observation about how real debugging actually works. When something breaks in production or sandbox, you're not starting with a neat project plan. You're responding to a failure. Legacy tools kept runtime information close at hand, which helped. But project-oriented IDE workflows like VS Code can introduce more state and more cognitive overhead for short investigative tasks.
Web Console is built to bridge that gap — keeping the investigation close to where the issue surfaced, while giving you a modern editing and debugging experience. Less window-hopping, less context switching, faster path to understanding what happened.
Real-World Workflow: Debugging an Apex Job Failure
The blog post uses Apex job failures as the clearest example of where Web Console makes an immediate difference. According to the official walkthrough, here's what the end-to-end flow looks like entirely within Salesforce:
No switching between tools. No manually reconstructing the context. The IDE meets you at the point of failure.
Production vs. Non-Production: The Guardrails
This is an important distinction from the official blog that developers need to understand before using Web Console:
How to Enable Web Console (Beta)
According to the official blog, Web Console is available across Salesforce orgs and editions from April 14, 2026 through admin opt-in. It is off by default. Here's how to turn it on:
- Go to Setup in your org
- Search for Web Console
- Open the Web Console Setup page
- Enable the feature and save
Full setup documentation is available on the official Web Console Beta documentation page.
Web Console vs. Developer Console vs. VS Code — Where Does It Fit?
The blog post is clear that Web Console is not trying to replace VS Code for sustained, project-oriented development. And it's not a feature-for-feature replacement of Developer Console either. It's filling a specific gap: the high-frequency, reactive debugging and investigation work that developers do when something breaks.
| Tool | Best for |
|---|---|
| Web Console | Debugging, log inspection, SOQL, quick fixes — directly in Salesforce, in context |
| VS Code + SF CLI | Sustained development, version control, CI/CD, complex multi-file projects |
| Developer Console | Legacy — now superseded by Web Console for most in-org tasks |
Gotchas to Watch Out For
Key Takeaways
- Beta available from April 14, 2026 across all Salesforce org editions
- Off by default — enable from Setup → Web Console Setup page
- Includes: debug log viewer, SOQL execution, Query Plan Inspector, Anonymous Apex, quick Apex edits, metadata navigation
- Production orgs: Apex is read-only. Sandbox / non-production: inline edits and saves supported
- Designed for reactive debugging workflows, not to replace VS Code for full project development
- Launches from Salesforce surfaces like Apex Jobs — you start from the problem, not a file tree
- Full docs at developer.salesforce.com/docs/platform/webconsole/overview
If you regularly find yourself bouncing between Salesforce and the old Developer Console or VS Code just to check a log or run a quick SOQL query, Web Console is worth enabling today. It's a beta — so expect rough edges — but the core workflow it targets is one every Salesforce developer has felt pain around for years.
📄 Source: Introducing Web Console (Beta): Code Where You Build on Salesforce — Salesforce Developers Blog
0 Comments