SDK Documentation

Each SDK has its own guide for building Dagger modules in that language. These guides assume you've read the Module Developer Guide for the platform model, and focus on language syntax, project layout, the development workflow, dependencies, testing, and troubleshooting.

Every SDK is itself a Dagger module — for example github.com/dagger/go-sdk — that provides the operations you use to develop a module: scaffolding a new module, regenerating bindings, managing dependencies, and pinning the engine version. See Developer Workflow for the shared flow; each page below shows the concrete commands for its language.

Choose your SDK

• Dang — Dagger's native DSL. No codegen and no build step: what you write is what runs. Best when your module orchestrates containers, files, and other Dagger objects.
• Go — Build modules in Go with a generated, typed client.
• TypeScript — Build modules in TypeScript with decorators and a generated client (Bun, Deno, or Node).
• Python — Build modules in Python with type hints, decorators, and a generated client.

More languages are planned. An SDK appears here once it has an official github.com/dagger/<lang>-sdk module.