- 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 ↗.
Introducing AIP Evolve: Coordinate AI FDE agents to improve AI systems in Foundry
Date published: 2026-09-08
AIP Evolve is now generally available for enrollments with AIP enabled and access to AI FDE. AIP Evolve coordinates fleets of AI FDE agents to improve AI systems in AIP. Define a target, optimization goal, validation strategy, and operational constraints, then review the resulting proposal and agent activity before merging changes.
Early adopters have used AIP Evolve to autonomously cut AI costs, improve eval performance, and migrate workloads to open source models. Learn more about AIP Evolve.
Key features
AIP Evolve supports iterative improvement workflows with the following features:
- Guided setup for model migration, cost reduction, latency reduction, evaluation score improvement, and custom goals.
- Flexible validation using selected test cases or existing evaluation suites.
- Configurable scoring criteria and acceptable output divergence.
- Agent constraints that control permitted change types and the maximum number of iterations.
- A proposal view containing proposed changes, validation results, output comparisons, supporting evidence, and confidence assessments.
- An interactive agent graph for monitoring progress and inspecting agent goals, insights, and artifacts.
- Integration with Global Branching for reviewing proposed changes before merging.
- The ability to resume an evolution in AI FDE with additional instructions.
Requirements
To use AIP Evolve:
- Enable AIP and ensure that you can access AI FDE.
- Install the AIP Evolve Marketplace product in an Ontology.
- Ensure that you have access to the target resource and any data or evaluation suites used for validation.
Getting started
The AIP Evolve setup screen, showing the Review stage with a fully specified evolution.
Open AIP Evolve and select New to create an evolution. Select the Foundry resource you want to evolve, then configure the following:
- Goal: Choose a predefined optimization goal or describe a custom objective.
- Validation strategy: Define the test data, scoring approach, and acceptable output divergence.
- Agent constraints: Select the types of changes agents may propose and set an iteration policy.
Review the generated prompt, then select Evolve. AIP Evolve opens AI FDE in a new tab and starts the evolution. You can also select Write custom prompt to provide your own instructions.
An example AIP Evolve proposal, where the system presents a model swap for cost reduction and the evidence that supports why the change is safe to make.
Open Evolutions to monitor active and completed evolutions. Use Proposal to review results and proposed changes, or Agent graph to inspect the agents involved in the evolution. When a proposal is ready, open it in Global Branching for final review and merging.
The AIP Evolve agent graph, showing each of the subagents that were spawned along the way to optimize the target AI component.
Your feedback matters
As we continue developing AIP Evolve, we welcome feedback about your experience. Share your thoughts with Palantir Support channels or our Developer Community ↗ using the aip-evolve tag ↗.
Introducing Vulcan, a CAD review application for the Ontology
Date published: 2026-09-08
Vulcan is a 3D visualization application that renders engineering geometry directly from Ontology data. Mesh models (GLB, GLTF, STL, OBJ, PLY, and 3MF), 2D engineering drawings (DXF), and point clouds (LAS and LAZ) can be loaded without conversion, and a single scene can contain all the models needed for a workflow. Vulcan is available in beta across all enrollments starting the week of September 7.
When saved, annotations, measurements, and section planes created in Vulcan are written to the Ontology as objects. A flagged defect can be used to trigger an alert, a critical dimension can be tracked in a dashboard over time, and a saved cross-section can be retrieved or shared with another team. Vulcan runs as a standalone application and can also be embedded in Workshop as a widget, where camera position, part selection, and measurement results can be connected bidirectionally to Workshop variables.
The part tree lists each part instance in the assembly; each instance corresponds to an object in the Ontology. Model source: Printables. Released under a Creative Commons public-domain license.
Vulcan has Ontology-backed tools to support cross-team workflows:
- Measure distances on models
- Create annotations
- Slice models with section planes
- Apply colors to parts with Ontology actions
Annotations and measurements on a CAD model in Vulcan. Model source: Printables. Released under a Creative Commons public-domain license.
See how Vulcan can support your production workflows:
- Markup models to provide instructions for assembly or repair procedures
- Share annotations and measurements across design-review teams
- Color models according to inventory levels or failure rates
- Visualize the results of automated design-verification runs in the Palantir platform
- Use components and models imported into Vulcan for further analysis across the Foundry application suite
To get started, load a CAD model into the viewport and select Add to scene. To learn more about the tools, the Workshop widget, and the Ontology object types and actions that Vulcan reads and writes, review the Vulcan documentation.
Your feedback matters
We want to hear about your experiences using Vulcan in the Palantir platform and welcome your feedback. Share your thoughts with Palantir Support channels or on our Developer Community ↗ using the vulcan tag ↗.
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.