The new stl skills command installs a Stainless CLI skill into your project so coding agents like Claude Code, Codex, and Gemini can learn how to use the Stainless CLI. It auto-detects whether your project uses .agents/ or .claude/ and installs to the right location, with…
npx @buildinternet/releases get stainlessStainless shipped several platform-level capabilities over the past 90 days, with notable momentum around CLI tooling, developer-facing docs, and AI-assisted workflows.
The CLI generator reached general availability, turning APIs into high-quality command-line tools. Follow-on improvements added binary endpoint downloads — generated CLIs now handle file-downloading endpoints with --output/-o flags and smart filename selection. The stl skills command also shipped, installing Stainless CLI skills into agent contexts (Claude Code, Codex, Gemini) with auto-detection for .agents/ vs .claude/ project layouts.
Stainless Docs Platform entered public beta for all new and existing projects, giving teams a managed documentation layer alongside their generated SDKs.
SDK generation picked up several targeted improvements. Per-endpoint security support fixed a bug where SDKs sent both api-key and Authorization headers simultaneously, causing auth errors against APIs with multiple schemes. A new omit_stainless_headers config flag removes X-Stainless-* headers from generated SDKs entirely. Python SDK builds gained PyPI trusted publishing via OIDC alongside existing API token support. Java builds added staging Maven repos, surfaced through the Studio build status panel.
AI-generated commit messages launched in opt-in form — Stainless now auto-generates Conventional Commits-formatted messages for each SDK build. GitHub release asset uploads also shipped, enabling bundled artifacts and documentation files to be attached to tagged releases.
Stainless Docs Platform is now available in public beta for all new and existing Stainless projects. Learn more in the announcement blog post here.
This is useful for uploading bundled or compiled artifacts or additional documentation files to your GitHub release.
You can now omit all X-Stainless-* headers from generated SDKs by adding the omit_stainless_headers to your Stainless config:
Generated CLI tools now support endpoints for downloading files using raw file data. The output destination can be specified with --output / -o flags, or if unspecified, a smart filename will be chosen to avoid overwriting local files. Files can also be sent through pipes or IO…
The details on how to use this repo are visible when clicking on the info icon in the “Build” row in the build status panel in the studio. We also generate a custom doc page in the repo root, which is viewable by clicking on the “Learn more” link in the popup.
Previously, the SDK sent both the api-key and Authorization headers, which could cause authentication errors depending on how your API handles multiple authentication schemes.
The Python SDK generator now supports publishing to PyPI using trusted publishing via OIDC in addition to API tokens.
The CLI generator is now generally available, which lets you turn your APIs into high-quality command line tools. Here are some highlights:
Stainless can now automatically generate commit messages for your SDK builds using AI. When enabled, AI generates descriptive commit messages for each SDK following the Conventional Commits format.