Feature Guide
osdk manages language runtimes, ecosystem tools, model snapshots, download sources, and shared caches through one command surface. This page is only an index; each topic page documents the complete command forms, parameters, and current implementation boundaries.
Start here
| Guide | What it covers |
|---|---|
| Getting Started | Global options, install/switch/query/remove workflows, and version aliases |
| GitHub Actions | Install osdk, restore shared caches, materialize locked tools and dependencies, and export the project environment in CI |
| Projects and Configuration | Project discovery, native version files, the complete configuration schema, merge rules, and trust |
| Project tasks | Declare project commands under [tasks] and run them with osdk run, with dependencies, parallel steps, and platform variants |
| Reproducible Lockfiles | How lock, install, outdated, and upgrade interact, including stale states |
| Runtimes and Ecosystem Tools | Node.js, Python, Java, Go, Rust, Maven, Gradle, and Kotlin |
| JavaScript Package Managers | npm, pnpm, Yarn, Bun, Deno, Node dependency handling, and registry preflight |
| npm Developer Tools | Install, pin, execute, upgrade, and restore npm CLI packages with npm:<package> |
| Cargo Developer Tools | Install registry crates or HTTPS Git repositories with an exact managed Rust toolchain |
| Go Developer Tools | Install module command packages with one exact managed Go toolchain and a selected proxy |
| Direct HTTPS Artifacts | Install an exact checksum-pinned file or archive from a strict HTTPS {version} template |
| Model Snapshots | Hugging Face, ModelScope, file filters, verification, locking, and environment adapters |
| Sources and Supply-chain Security | Mirrors, offline mode, pre-releases, checksums, signatures, attestations, and GitHub Releases |
| Container Runtimes, Registries, and Native Operations | Runtime/cache diagnostics, anonymous OCI registry tests, built-in Docker Hub mirror benchmarking, safe native mirror apply, direct native image pulls, and preview-bound cleanup |
| Storage, Shell, and Extensions | CAS, caches, directories, shims, activation, temporary execution, completions, diagnostics, and declarative backends |
Common paths
After installing osdk, continue with the guide that matches your goal:
- To define a repository's tool versions, read Projects and Configuration and Reproducible Lockfiles.
- To reproduce the repository in CI with cache reuse, read GitHub Actions.
- To manage a language toolchain, read Runtimes and Ecosystem Tools.
- To pin npm, pnpm, or Yarn, read JavaScript Package Managers.
- To install Prettier, TypeScript, or a scoped npm CLI package, read npm Developer Tools.
- To install ripgrep or another Rust CLI from a registry or Git repository, read Cargo Developer Tools.
- To install gopls or another Go command package, read Go Developer Tools.
- To install a checksum-pinned executable or archive from a direct HTTPS URL, read Direct HTTPS Artifacts.
- To download a model repository, read Model Snapshots.
- To configure a corporate mirror or strict verification, read Sources and Supply-chain Security.
- To inspect Docker, containerd, Buildx, OCI registries, mirror plans/benchmarks/application, or native cache usage—or to pull an image or narrowly prune native data—read Container Runtimes, Registries, and Native Operations.
- To configure your shell, reclaim space, or add a data-only backend, read Storage, Shell, and Extensions.
For the internal request path through resolution, download, verification, CAS materialization, and shim dispatch, read Implementation.