Fix openAPI spec for exec

[sjmiller609]

No description provided.

[github-actions]

✱ Stainless preview builds

This PR will update the hypeman SDKs with the following commit message.

feat: Fix openAPI spec for exec

⚠️ hypeman-go studio · code

There was a regression in your SDK.
generate ⚠️ → lint ✅ → test ✅

go get github.com/stainless-sdks/hypeman-go@c35479bcb4e1a6c02484b2a7d27d9beac0ccee43

⚠️ hypeman-cli studio · code

There was a regression in your SDK.
generate ⚠️ → lint ✅ → test ⏳

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
Last updated: 2025-11-26 16:10:36 UTC

[mesa-dot-dev]

Mesa Description

This pull request addresses an issue with the OpenAPI specification for the exec API. The primary goal is to correct and update the API definition to accurately reflect the current exec functionality. This ensures that any generated API clients or documentation will be consistent and correct, improving overall API usability and developer experience.

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Performed full review of db26f38...f1bf1bc

Analysis

1. HTTP Method Semantics Misalignment: Changing from POST to GET for a WebSocket upgrade that executes commands contradicts RESTful principles since this endpoint performs actions with side effects rather than retrieving resources. This may introduce security vulnerabilities related to CSRF or caching.

2. Breaking API Change: The migration from POST to GET and moving parameters from query strings to WebSocket payload will break backward compatibility with all existing clients, requiring coordinated updates to client code.

3. Security Validation Requirements: The new optional fields (env, cwd, timeout) in the ExecRequest schema require thorough validation to prevent security exploits, particularly since they could potentially provide greater system access.

4. Documentation and Client Updates: This architectural change necessitates updates to documentation and client libraries before deployment to prevent integration failures.

Tip

Help

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{2 files reviewed | 0 comments | Edit Agent Settings • Read Docs}