News & Intel
LiveDaily AI-curated intelligence on Palantir Foundry, Ontology, AIP, Apollo, contracts, and community feedback. Updated automatically via GitHub Actions every day at 7 AM UTC.
Connecting Agents to Decisions
The Palantir Ontology Palantir’s software powers real-time, human-agent decision-making in many of the most critical commercial and government contexts around the world. From disaster response to nuclear energy production , our customers depend on Palantir AIP to safely, securely, and effectively leverage AI in their enterprises — and drive operational transformation. While many factors contribute to achieving and scaling operational impact, including our AIP AgentCamps — where customers are hands-on-keyboards and achieving outcomes with AI in a matter of hours — the key differentiator is a software architecture which revolves around the Palantir Ontology. The Ontology is a system designed to represent the decisions in an enterprise, not simply the data. The prime directive of every organization in the world is to execute the best possible decisions, often in real-time, while contending with internal and external conditions that are constantly in flux. Traditional data archit
AI FDE Error: Failed to load Workshop module due to missing Action Parameter RID
Context: I am a software designer who has been leveraging Claude Code extensively over the past year. I recently transitioned into Foundry and have been utilizing the AI FDE tool. Compared to manual configuration within Foundry, the experience has been excellent; I’ve successfully managed CRUD operations for object types, actions, and general Ontology metadata without issue. The Problem: I am now attempting to use AI FDE to iterate on our UI Modules (Workshop) . While I can reference the UI Module correctly, AI FDE fails during the “loading” phase with the following error: [Error] Failed to load Workshop module: No ID found for action parameter RID: ri.actions.main.parameter.14d4d52e-315f-4976-a7a7-92e261affbc3 (at config path: eb7403c7-16e7-4cd6-9c7e-2dab9b5c4526.actionConfigs.0.actionConfig) Troubleshooting Steps Taken: Baseline Validation: I created a fresh “sandbox” Workshop module to verify if AI FDE supports UI editing. This worked as expected—I wa
Additional Metrics in Workshop Granular Metrics
Would love to see more metrics being logged with Workshop > Metrics > Enable granular metrics. For instance, time and date, username, user department/branch, etc. At present only mid-level anonymized metrics are gathered (Actions vs. Submission Count, and Views (Pages, Overlays, Tabs) vs View Count, and the time frames are hard coded at 7, 30, 90 days. Customers are often interested in who used their app, what department they were from, when the app was used, and they may want to compare this month with last month, all things the present tool doesn’t support. A workaround can be implemented with hidden slate iframe that Workshop displays, and the Slate then runs a create log object action on page load, but if these features were built into Workshop Granular Metrics it would reduce complexity and increase maintainability (over the workaround with Slate iframes in Workshop to log). 1 post - 1 participant Read full topic
Question about object indexing, preserving the order / sorting of backing datasets
I tried sorting in pipeline builder a particular dataset, but when the object gets indexed the object’s order is completely different than the backing dataset’s. I initially thought this is a random shuffle but when I present the object in a table in workshop, there is a consistent order (unsorted) whenever I refresh the page. This brings up the question - in Palantir’s indexing process in an object set, how is the order determined? Is it completely random? Is there any way to preserve sort in pipeline builder to translate to the object level? (I feel like this defeats the purpose of sorting in pipeline builder)… Thank you! 1 post - 1 participant Read full topic
Expose Resource Lineage as a Public API
Foundry’s Workflow Lineage UI shows the full dependency graph between resources (datasets, object types, transforms, applications, monitors). This data is not accessible programmatically. Please expose it as a V2 REST API endpoint and MCP tool . Today this data is only available through the Workflow Lineage UI and AI FDE’s internal tooling. Functions, AIP Agents, and OSDK apps cannot access it. What We Tested From a TypeScript v2 Function, we tried 30+ API paths including Compass sub-paths, decorations, V2 endpoints, and all @osdk/foundry.* SDK packages. None expose lineage data. Meanwhile, AI FDE’s internal get_resource_lineage tool returns exactly what we need — upstream/downstream RIDs with names, paths, and connection types. The Ask REST API — GET /api/v2/resources/{rid}/lineage for Functions, OSDK apps, and scripts MCP Tool — get_resource_lineage for external AI agents (Claude Desktop, etc.) AIP Agent Platform Tool — Same capabi
Object edits conflict resolution strategy not working as expected
Hello, I am trying to understand why a property value is not propagating from my backing dataset to my object type for newly created objects. I have created a minimal test object with the following backing dataset and properties: Next, I have an action to create new objects of this type — which sets Key and Value 1, but not Value 2: I executed the action to create a new object: Next, I added this row to the backing dataset, with the goal being to populate Value 2 in my edits-created object: At this point, what I expect to happen and what actually happens diverges: Expectation: my object 72ac8812 should have Value 1 of new object from actions (because Conflict resolution strategy is set to “Apply user edits”) and Value 2 of bar (because this property was never edited) Reality: the object still has Value 2 of null after the dataset synced My expectation is that the conflict resolution happens by property
insert react/OSDK(pilot-app) in workshop
Currently there are 2 possible approaches to do this: create custom react widget (clear) create a react app using pilot-app We need the second as we want to deploy it as a standalone app with a url, but we would like to also integrate it in Workshop. I followed this steps: https://www.palantir.com/docs/foundry/workshop/widgets-iframe#step-1-modify-your-custom-application-to-communicate-with-workshop But when doing it, there seems to be an issue with the domain, as now it is allowed child-src ‘self’ blob: mailto:; connect-src ‘self’ blob: https://AAAA.AAA.bb wss://https://AAAA.AAA.bb; default-src ‘self’ https://AAAA.AAA.bb; font-src ‘self’ data:; frame-ancestors ‘self’ https://AAAA.AAA.bb; img-src ‘self’ blob: data:; media-src ‘self’ blob:; script-src ‘self’; style-src ‘self’ ‘unsafe-inline’; worker-src ‘self’ blob:; but the application has this domain: APPNAME. AAAA.AAA.bb So I dont know how to proceed as it seems that X-Frame-Options is not allowing
Append/incremental file management
I’m frequently running an incremental transform/append sync and the numbers of files in my dataset is growing too large. How can I manage this? 2 posts - 1 participant Read full topic
What's the best Vibe-Code set up for foundry/repo dev?
I was given an opportunity to try out Foundry developer account a few days ago and the platform’s been pretty powerful and amazing. I discovered AI FDE so I was making Workshop module with that for a bit, and then I realized, I should probably leverage OSDK via developer console. But tbh, the Continue extension has been quite slow in its outputs and task speed, overall clunky feeling. Now I am thinking of just cloning it locally, and using Palantir MCP with my own Claude Code or Cursor, but would be eating up my weekly token quota… What are y’all’s set up for this?? 2 posts - 2 participants Read full topic
Workshop - Global / Workspace-Level Saved Colors Shared Across All Modules
Hi Palantir team and community, First off, the recently shipped Module Saved Colors feature is a great step forward — being able to define a color palette at the module level and have it propagate to all widgets and sections within that module is really useful. However, we now have a natural next-level problem: we have multiple Workshop modules that need to share the same color palette , and there is currently no way to define colors once and have them apply across all modules. The Problem When building a suite of Workshop modules (for example, 10 modules across a workspace), every module that uses the same brand or theme color requires the same saved color to be manually re-defined inside each module individually. If our brand color changes — say from #3A86FF to #2563EB — we have to go into every single module and update it one by one. This is time-consuming, error-prone, and not scalable. What We’re Asking For A Workspace-level or Space-level Global Color P
workshop view not there
Hello, I am doing my first end to end workflow with speed run course and once I get to the Assign order I am unable to move onto THE WORKSHOP. I do not see any grid and somewhere below where it says Workshop the value is zero and it is empty. Do I lack permission? Thank you 1 post - 1 participant Read full topic
We translated the Palantir manifesto for actual human beings (The Verge)
The Verge: We translated the Palantir manifesto for actual human beings — What happens when an all-seeing eye looks in the mirror? … Palantir CEO Alex Karp is a man in charge of one of the most important and frightening companies in the world. Karp's new b…
Email Notification trigger on Automation
I’d like to replace “Palantir Foundry” with a custom name. Currently, I’m using the Notification trigger in the Automation app to send emails to users, but the email header displays “Palantir Foundry.” How can we change this to show our custom name instead? 1 post - 1 participant Read full topic
Recent Datatype Changes using lightweight
We have observed a recent change in Foundry that affects how data is read and written when using transforms.api.LightweightInput . It appears that the automatic datatype harmonization previously applied in Lightweight transforms has been disabled or changed. As a result, this can cause compatibility issues between “Foundry datatypes” and “Other datatypes”, especially when certain types are not supported on one side or were previously auto‑cast. Observed Issues MapType columns with Polars input Reading a dataset that contains a MapType column via input.polars() now results in a build-time error: ValueError: Discovered an input column 'MAP' in the Foundry schema which is a Map type. Polars does not support Map types. Please use another runtime, convert this column to Struct if possible, or remove this column from the schema of the input dataset. Previously, this MapType was automatically cast to a pl.Struct , so no manual intervention was required. Non-
Feature Request: Global Color Palettes and Variable-Driven Colors in Workshop
I would like to request the addition of global color palettes in Workshop, so that saved colors can be used across all modules for consistent branding and centralized management. Additionally, it would be valuable to support variable-driven color input, allowing string variables (such as hex codes) to be used as input for widget colors and enabling dynamic color changes based on variable updates. Are there any current workarounds or plans to support these features? 1 post - 1 participant Read full topic
Budget Leak Reveals DHS Is Creating Smart Glasses for ICE
The Department of Homeland Security is developing smart glasses that would allow federal agents to identify people using biometric data in real time. Journalist Ken Klippenstein, citing a budget request from DHS, reports that these devices, slated to be relea…
Frontend Engineering at Palantir: Engineering Multilingual Collaboration
Frontend Engineering at Palantir: Building Multilingual Collaboration About this Series Frontend engineering at Palantir goes far beyond building standard web apps. Our engineers design interfaces for mission-critical decision-making, build operational applications that translate insight to action, and create systems that handle massive datasets — thinking not just about what the user needs, but what they need when the network is unreliable, the stakes are high, and the margin for error is zero. This series pulls back the curtain on what that work really looks like: the technical problems we solve, the impact we have, and the approaches we take. Whether you’re just curious or exploring opportunities to join us, these posts offer an authentic look at life on our Frontend teams. In this blog post, Rahma, a frontend engineer based in CA, shares how building Dossier’s translation mode — a recent project she tackled at Palantir — deepened her appreciation for frontend engineeri
AI FDE create_object_type defaults to Object Storage V1 — no way to select V2 at creation time
TL;DR When creating an Object Type through the AI FDE create_object_type tool, the Object Type is always registered against Object Storage V1 (Phonograph) . The tool does not expose a parameter to select Object Storage V2, and OSv2 does not appear to be the default. This forces a manual post-creation migration from Ontology Manager, which is expensive for large Object Types. Requesting that OSv2 be made the default — or, at minimum, that an objectStorageVersion parameter be exposed. Environment Feature: AI FDE → create_object_type Object Type: ~702M rows, 59 properties, 2 many-to-one link types Source dataset: Pre-processed transactional dataset in Foundry Link targets: Store (via store ID), Product (via SKU) What happened Using AI FDE end-to-end, I: Added composite PK and foreign-key columns ( SELL_IN_ID , store FK, SKU FK) to the source dataset via a transform. Validated match rates against the Store and Product m