Stainless

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 symlink support when both exist.

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 symlink support when both exist.

Stainless Docs Platform is now available in public beta for all new and existing Stainless projects. Learn more in the announcement blog post here.

Stainless Docs Platform is now available in public beta for all new and existing Stainless projects. Learn more in the announcement blog post here.

You can now upload GitHub release assets when an SDK is published:

targets:
  # Or any other target
  typescript:
    publish:
      release_assets:
        github:
          - ./path/to/what/you/want/to/upload
            # Or this
          - name: Display Name
            path: ./path/to/what/you/want/to/upload
          # As many as you want...

This is useful for uploading bundled or compiled artifacts or additional documentation files to your GitHub release.

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:

client_settings:
  omit_stainless_headers: true

This is particularly useful if your API has a headers allowlist that rejects requests containing unknown headers.

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

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

When a Java SDK build completes successfully, Stainless will generate a hosted Maven repo that can be shared for early testing, before the SDK is formally released.

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.

A similar feature has been available for Python and Typescript builds for a while; with this change, sharing and testing pre-release Java builds is just as easy.

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.

SDKs now correctly respect per-endpoint security definitions in your OpenAPI spec. Previously, if an endpoint only listed one security scheme, the SDK would still send all configured auth headers. Now the SDK only sends the headers required by the scheme(s) configured for that specific endpoint.

This is enabled by default for new projects. To enable for existing projects, update the edition in your config to 2026-01-30 or higher:

edition: "2026-01-30"

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.

To learn more, see our docs on publishing.

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:

• Built-in support for streaming and paginated endpoints using command line paging tools
• Automatically generated man pages and --help documentation
• Shell completion with smart suggestions
• Interactive TUI views for exploring deeply nested data
• Easy integration with AI agents that can run shell commands

Check out the documentation to get started or the launch blog for more info.

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.

How to enable:

• Navigate to your organization settings at https://app.stainless.com/{your-org}/settings and toggle AI Commit Messages on
• Preview PRs: Set enable_ai_commit_messages: true in your GitHub Action workflow
• Studio: Use the "Generate with AI" option when building from a dev branch
• CLI: run str builds create with the --enable-ai-commit-messages flag

Learn more about AI commit messages →

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.