Orgbench

Product updates

What changed in Orgbench, newest first.

2026-09-07

Linux x64

The VS Code extension 0.1.2 is now available as orgbench-linux-x64.vsix alongside the macOS and Windows builds, and the IntelliJ plugin 0.1.1 bundle carries the Linux x64 core binary. The Linux core is statically linked against musl, so it does not depend on a particular system libc version. Linux on ARM has no build.

All files are on the downloads page. The VS Code documentation describes the Linux install path.

2026-08-21

Permission transfer, session export, editable diffs

The IntelliJ plugin and the VS Code extension picked up a set of improvements this week.

  • Permission transfer grew from field-level security into six kinds of permissions: fields, objects (including View All Fields), Apex classes, Visualforce pages, tab visibility and record type visibility. Screens and labels are renamed from FLS to Permissions. Permission containers now show their Setup label and are matched by Id and metadata fullName, so profiles whose Setup name differs from the metadata name — Standard User versus Standard — no longer drop out of the list.
  • Session export and import replace the package.xml manifest buttons. Export Session writes a JSON scenario with both endpoints, the manifest, checked rows, the permission mode, test classes, containers and the deploy mode; Import Session pre-fills the wizard from such a file. Manifest support itself stays in the core.
  • Editing in the difference view extends from Apex classes and triggers to any single-file component: Visualforce pages, objects, fields, flows, layouts and others. Bundles and container files stay read-only.
  • Best-effort deployments send the whole selection as one package: components Salesforce accepted stay deployed, rejected ones are the only Failed rows. Names, methods and messages of failed Apex tests are shown in every deploy mode.
  • Unmanaged children of managed-package objects — fields, list views, validation rules and others — are compared and deployed; the packaged object itself still is not.
  • The Custom Object comparison schema grew from 8 to 20 attributes, so an object created in the target keeps the capabilities enabled on the source, and its fields are no longer rejected because of disabled feeds.

The IntelliJ and VS Code documentation pages reflect the changes.

2026-08-07 · 0.1.1

Orgbench 0.1.1

Both clients ship a bundled native core for macOS arm64, macOS x64 and Windows x64. Linux is planned.