- Capabilities
- Getting started
- Architecture center
- Platform updates
Announcements
REMINDER: Sign up for the Foundry Newsletter to receive a summary of new products, features, and improvements across the platform directly to your inbox. For more information on how to subscribe, see the Foundry Newsletter and Product Feedback channels announcement.
Share your thoughts about these announcements in our Developer Community Forum ↗.
Use VS Code workspaces as your default code editor
Date published: 2026-09-03
Starting the week of September 14, 2026, VS Code workspaces will become the default code editing environment for supported repository types in Foundry.
An example VS Code workspace, displaying the default welcome page.
VS Code workspaces provide automatic environment setup, responsive language support, an integrated terminal, and AI-powered development assistance with Continue. For Python transforms, workspaces also support full-data previews and production-equivalent incremental previews. Development runs on Palantir infrastructure, so input data remains on the platform.
The Editor preference setting in a VS Code workspace.
To change your default editor preference, navigate to the Settings tab, then Preferences > Editor preference. Depending on the selected editor, a list of unsupported repository types for that environment will appear. If you attempt to open a repository that is not supported by the default editor, the repository will instead open in the fallback environment (typically Code Repositories).
Learn more about the benefits of VS Code workspaces and supported workflows.
Visual rebasing makes Workshop changes easier to resolve
Date published: 2026-09-03
When multiple builders update the same Workshop module on different branches, rebasing incorporates changes from main into a branch before that branch is merged. Workshop now provides visual rebasing to help reconcile granular changes to widgets, sections, and variables between main and your branch.
Previously, you had to inspect the module’s JSON definition in the Changelog panel to determine what changed. Visual rebasing brings this workflow into the module editor, where you can accept, reject, or combine changes while seeing how they affect your module.
The rebase dialog lets builders start a visual rebase or reject all changes from main.
Understand changes in context
During rebasing, change icons appear beside the affected settings in widget and section configuration panels. The icons distinguish additions, modifications, deletions, shifts, and conflicts, so you can locate changes without leaving the configuration you are reviewing. Select an icon to open a detailed view of main and your branch side by side.
- Conflict: The same property for the same component was edited on
mainand the branch. - Addition: A property or component was added.
- Modification: A property or component was edited.
- Deletion: A property or component was deleted.
- Shift: A section or widget was moved to a different parent.
- Branch: A property or component was resolved using the branch version.
The change icon legend identifies differences between the two versions.
The review changes dialog compares the metric card configuration on main with the configuration on your branch.
Variable conflicts use the same workflow. Select a conflicting variable to open its editor and compare the complete definition and settings for each branch.
How to preview, accept, and combine changes
By default, Workshop automatically accepts non-conflicting changes from main and merges them into your branch. You only need to take action when the same configuration field, variable definition, or layout position was changed on both branches.
Select Main branch or Your branch to preview a configuration temporarily and see its effect on the module. You can accept either version as-is or use one as a starting point for further edits. Those edits create a Current session state that can combine changes from both branches.
To replace the entire module configuration from main with the branch configuration, select Reject all changes from main when you start the rebase. This causes the branch configuration to override changes from main when you merge the branch. Use this option only when you want to discard all incoming changes.
What's next
Future updates to visual rebasing will support layout shifts and changes to module-level settings.