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 ↗.
Date published: 2026-06-09
Faster pipelines now accept media sets as inputs. You can process PDFs, images, and audio files in a Faster pipeline and convert them into structured data for downstream extraction, classification, analysis, or review.
For more information, see the media sets documentation.

Use media sets in Faster pipelines to transform media file inputs.
With media set support in Faster pipelines, you can now build pipeline workflows that take PDFs, images, and audio files as direct inputs. Supported use cases include:
Ensure your media files are uploaded to a new media set.

Select the upload to a new media set option when uploading media files
As we continue to add features to Pipeline Builder, we want to hear about your experiences and welcome your feedback. Share your thoughts with Palantir Support channels or our Developer Community ↗ using the pipeline-builder tag ↗.
Date published: 2026-06-04
Starting the week of June 22, editing Python transforms in Code Repositories will move to the legacy phase of development. VS Code workspaces are the recommended environment for editing Python transforms, offering AI-powered coding assistance, full dataset preview, an optimized language server, and an integrated terminal.
The Code Repositories editor will remain supported and available, with future feature development focused on VS Code workspaces. Code Repositories remains the recommended editor for other repository types, including Java and SQL transforms.
If VS Code workspaces are unavailable on your enrollment, Code Repositories remains the recommended way to author Python transforms.
To get started with VS Code workspaces for Python transforms, we recommend reviewing the following documentation:
Date published: 2026-06-04
Faster pipelines in Pipeline Builder now support more than 25 built-in GeoExpressions for cleaning, transforming, and visualizing geospatial data without needing to leave the platform or write custom code. Supported operations include geometry intersections, GeoJSON parsing, GeoPoint conversions, and more.
To learn more, see GeoExpressions in Pipeline Builder.
The team is actively adding more GeoExpressions which will automatically become available for your Faster pipelines.

The Geospatial option from the Transform board menu.

Geo Preview in Pipeline Builder.
geoshape type. To learn more, see using geospatial data with the Ontology.Send feedback through Palantir Support or the Developer Community using the pipeline-builder tag.
Date published: 2026-06-02
Claude Opus 4.8 is now available on non-georestricted enrollments from Anthropic, AWS Bedrock, and Google Vertex. For US, EU, and non-georestricted enrollments, the model is available from AWS Bedrock and Google Vertex. For JP georestricted enrollments, the model is available from AWS Bedrock.
Claude Opus 4.8 adds improvements in coding, long-running autonomous agents, and reasoning on complex enterprise problems. For more information, review Anthropic's model documentation ↗.
To use this model:
We want to hear about your experiences using language models in the Palantir platform and welcome your feedback. Share your thoughts with Palantir Support channels or on our Developer Community ↗ using the language-model-service tag ↗.
Date published: 2026-06-01
The Variable lineage graph is now generally available in Workshop. The graph replaces the previous variable dependency graph with a redesigned visualization for tracing how variables and widgets in a module depend on one another. Use it to debug recompute behavior, find which widgets read or write a given variable, and better understand complex relationships between your application's components.

The Variable lineage graph mode shows variables, widgets, and their dependencies.
To open the new variable lineage panel, select the Graph button on the top right of the Variables panel in any Workshop module's edit mode.

Use the Graph button, highlighted in red, to open the variable lineage panel.
Each node on the graph represents a variable or widget. Nodes with dependencies now have chevron arrows on its top and bottom edges. Selecting an arrow expands a node's parents or children to trace a chain of dependencies through a large module. Show all and Clear actions in the header let you expand to the full application graph or remove all nodes. Undo and redo buttons in the header step backward and forward through expand, collapse, and selection actions.

A detailed view of variable usage and computation time.
Variable nodes are tagged with the pages and overlays where they are used. Toggle Show pages and overlays in the header to open a legend that lists each referenced page and overlay, alphabetized and split into separate sections. The legend only includes pages and overlays that appear on visible nodes so the list stays scoped to what you can actually see in the graph.
Toggle Show computation time in the header to display per-variable timing information. Variables that take longer to recompute may be candidates for restructuring: for example, splitting a complex function-backed variable into smaller pieces or changing the recompute behavior on upstream variables to avoid unnecessary work.
To read more about the variable lineage graph, see Workshop's documentation on variables.
We want to hear about your experiences using Workshop in the Palantir platform and welcome your feedback. Share your thoughts through Palantir Support channels or on our Developer Community ↗ using the workshop tag ↗.