Package
OSDK CLI
The operational CLI for deploys and selected generation workflows; most mature on shipping/runtime operations rather than compiler internals.
- Handles site deployment, snapshots, version inference, and operational workflows around third-party apps.
- Matured deploy ergonomics before Palantir exposed much of the compiler stack.
- Uses public Foundry third-party-application APIs underneath site deploy flows.
Relevant code
Most revealing source snippet
published: build/esm/siteDeployCommand-PLEDSCX7.js
packages/cli/src/commands/site/deploy/siteDeployCommand.mts
open source file ->if (snapshot) {
await uploadSnapshot(clientCtx, application, siteVersion, snapshotId ?? "", archive);
return;
}
await upload(clientCtx, application, siteVersion, archive);
const website = await thirdPartyApplications.deployWebsite(clientCtx, application, {
version: siteVersion,
});Notes
Why it matters
This package is the oldest major public layer in the story.
The meaningful features here are not recent patch bumps. They are the shape of the public contract: site deployment, snapshot upload, auto-versioning, preview links, and widget/site operational commands all landed before the newer OAC compiler pieces were visible.
The deploy command is especially revealing because it is not doing hidden magic. It zips a directory, uploads a version through the third-party applications API, and either deploys it live or returns a preview link. That is a very concrete public ops surface.
That timeline helps explain why the public stack can feel more mature at the deploy end than at the compiler end.