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 ↗.

---

GPT-5.5 is now available in AIP

Date published: 2026-05-05

GPT-5.5 is now available from Azure on US and EU georestricted, and non-georestricted enrollments. The model is available from OpenAI on US georestricted and non-georestricted enrollments.

Model overview

GPT-5.5 is OpenAI's newest model, excelling at agentic coding, debugging, research, tool calling, and a wide range of other tasks. For more information, review OpenAI's model documentation ↗.

• Context window: 1,050,000 tokens
• Knowledge cutoff: December 1, 2025
• Modalities: Text, image
• Capabilities: Reasoning tokens, function calling, structured outputs

Getting started

To use this model:

• Confirm that your enrollment administrator has enabled the relevant model family.
• Review token costs and pricing.
• See the complete list of all available models in AIP.

Your feedback matters

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 ↗.

---

Global Branching is generally available May 18: branch, test, and merge across applications

Date published: 2026-05-05

Starting the week of May 18, 2026, Global Branching (formerly Foundry Branching) will be generally available to all users on all enrollments. Global Branching provides a shared workflow to make changes across multiple applications on a single branch, test those changes end-to-end without disrupting production workflows, and merge them back into Main. Consult the Global Branching documentation to learn more.

Reviewing main branch updates and resource check status in Ontology Manager.

Supported applications and workflows

Global Branching is available for transforms and TypeScript v1 functions repositories, Pipeline Builder, the Ontology, Workshop, AIP Logic, and Object Views.

A proposal overview showing resources, approval status, and the "Do not merge proposal" setting.

For these applications, the following workflows are supported:

• Branch and modify resources: Create or access a branch, and make changes to resources without affecting the Main branch.
• Remove resources: Remove a resource from a branch to reset it to its state on the Main branch.
• Include new updates from Main and resolve conflicts: Rebase your branched resource to update it with the latest changes from the Main branch. If conflicts exist, you will be redirected to the appropriate application to resolve them.
• Protect resources: Resource owners can protect resources so that changes must go through a branch and receive approval before merging.
• Define approval policies: Project owners define approval policies specifying eligible reviewers, required approvals, and whether contributors can self-approve. For Code Repositories and Pipeline Builder, you define policies within the resource itself.
• View branched resources: Use Data Lineage to inspect the branched state of your resources and trace how changes propagate.
• Clear all checks and merge changes: When a proposal is created, the system runs checks on each resource to surface issues such as conflicts or missing approvals. Once all checks pass, you can merge your proposal.

Updated security model and branch lifecycle

When Global Branching is GA, the security model and branch lifecycle will feature:

• Simplified merge permissions: Previously, merging required a dedicated branch role. Going forward, any user who can view a proposal can merge it once all approvals and checks are satisfied. A new Do not merge setting allows branch owners to block merges until they are ready.
• Revamped branch lifecycle: Inactive branches will have ontology resources de-indexed and data eventually deleted, but all logic is preserved. Branches will no longer be auto-closed. Instead, branches can be manually archived and restored at any time.

Restricted Views, Automate, and what's ahead

Restricted Views and Automate are now available in beta. The core branching workflow is functional, but some GA-level features — such as approval integration and removing a resource from a branch — are not yet available. Contact Palantir Support to enable, and consult the application-specific documentation to learn more about each application's current scope.

Beyond these two applications, we are actively working to expand branching support across the Palantir platform, starting with OSDK, TypeScript v2 and Python functions, and Developer Console.

Your feedback matters

Have thoughts on Global Branching? Let us know through Palantir Support channels and our Developer Community using the global-branching tag ↗.