# why
We don't want the MCP server showing up in readme files for the
generated sdks
# what changed
Removed it from the stainless yaml for now - this means no MCP commits.
# test plan
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Disabled the MCP server in stainless.yml to keep it out of generated SDK
READMEs. This prevents MCP-related content and commits for now.
<sup>Written for commit 090a47edcd62b8b5c8e58843cf913dc7e5c12825.
Summary will update on new commits. <a
href="https://cubic.dev/pr/browserbase/stagehand/pull/1639">Review in
cubic</a></sup>
<!-- End of auto-generated description by cubic. -->
Co-authored-by: ci-test <ci-test@example.com>
# why
# what changed
# test plan
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Enables publishing for Java/Kotlin (Maven), PHP (Packagist), and C#
(NuGet), and fixes event-stream “finished” detection. Also aligns
project naming and updates the Python repo target in Stainless.
- **Refactors**
- Set project_name to “stagehand” and removed the alpha name.
- Updated Python production_repo to browserbase/stagehand-python
(removed branch suffix).
- Turned on publishing: Maven (Java/Kotlin), Packagist (PHP), NuGet
(C#).
- Updated commented local env URL to http://stagehand-api.localhost.
- **Bug Fixes**
- Adjusted streaming on_event to detect finished using the JSON prefix:
'{"data":{"status":"finished"'.
<sup>Written for commit 8cd5e7a754a3f544cff42f9ca98cfa2460da2ed9.
Summary will update on new commits. <a
href="https://cubic.dev/pr/browserbase/stagehand/pull/1638">Review in
cubic</a></sup>
<!-- End of auto-generated description by cubic. -->
# why
Fixes: https://github.com/browserbase/stagehand-go/issues/43
Adds automatic bedrock AI SDK client support when `modelName ~=
'bedrock/...'`
# what changed
# test plan
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Adds automatic Amazon Bedrock support by routing models named
bedrock/{provider}.{model} to the Bedrock client. This enables
zero-API-key setup using your AWS credentials.
- **New Features**
- Route bedrock/... model names to @ai-sdk/amazon-bedrock.
- Treat Bedrock as no-API-key provider (uses AWS IAM/default
credentials).
- Example usage: bedrock/anthropic.claude-3.
- **Dependencies**
- Added @ai-sdk/amazon-bedrock as an optional dependency.
<sup>Written for commit e1d7c4c14e14b57120b10735cd8b4f898a987342.
Summary will update on new commits. <a
href="https://cubic.dev/pr/browserbase/stagehand/pull/1617">Review in
cubic</a></sup>
<!-- End of auto-generated description by cubic. -->
# why
# what changed
# test plan
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Expose the session replay metrics endpoint in the public API and
Stainless spec so SDKs can fetch run metrics. This lets clients retrieve
replay data for a session and optionally stream results.
- **New Features**
- Added GET /v1/sessions/{id}/replay to OpenAPI with ReplayResponse.
- Enabled SDK generation by adding replay to stainless.yml.
- Removed hide flag so the route appears in API docs.
- Supports optional SSE via x-stream-response header ("true"/"false").
<sup>Written for commit b7a44b9ae11632ecdf093ca3b3f6ba95d63a4c16.
Summary will update on new commits.</sup>
<!-- End of auto-generated description by cubic. -->
# why
Better to have in stainless yaml than gen-openapi script + some minor
cleanup.
# what changed
- Removed old v2 ModelConfigStringSchema from union
- moved all manual transforms out of gen-openapi.yml into stainless
transforms yaml config
- Confirmed no other v2 union types
- Added openapi.code_samples to stainless yaml as per mintlify/stainless
integration docs here:
https://www.mintlify.com/docs/integrations/sdks/stainless
# test plan
<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Moved Stainless compatibility transforms from gen-openapi.ts into
stainless.yml and removed the v2 string model config. This keeps
openapi.v3.yaml faithful to the Fastify/Zod output and applies
compatibility at SDK generation, improving CI stability and supporting
STG-1149.
- **Refactors**
- Removed string-based post-processing from gen-openapi.ts.
- Added openapi.transforms in stainless.yml to:
- Remove propertyNames.
- Set targeted additionalProperties to true.
- Add ProxyConfigList title for the proxies array.
- Mark StreamEventSystemData result fields as x-stainless-any.
- Marked NavigateResult result as x-stainless-any via schema overrides.
- Dropped ModelConfigString; ModelConfig is now object-only. Updated the
API client to convert agentConfig.model to the wire ModelConfig.
- Added openapi.code_samples: mintlify. Updated openapi.v3.yaml to the
raw schema (propertyNames present, additionalProperties {}, no injected
titles).
<sup>Written for commit 0c82c6c99462388777c02c7971a94b8c5b9d6d49.
Summary will update on new commits.</sup>
<!-- End of auto-generated description by cubic. -->
# why
Right now our server `/end` endpoint doesn’t match the production
Stagehand API contract: prod expects a non-empty JSON body when
`Content-Type: application/json` is set, so a call to `/end` that sends
an empty body fails. This change makes our server + OpenAPI spec match
prod so downstream generated SDKs send an empty object.
# what changed
Defined a strict empty-object request schema for `/end`
(`SessionEndRequest`) and made it a required request body in the route +
emitted OpenAPI. Updated the /end handler response to match prod `({
"success": true })` and added a server test covering the body
requirement.
- Also added a `stainless.yaml`
# test plan
Regenerate the Python SDK and verify sessions.end() succeeds against
production