Speakeasy CLIs Now Reject Flags That Break the OpenAPI Schema
Speakeasy 1.801.0, released Oct. 7, makes generated CLIs enforce a schema's pattern and maxLength on string flags, and drops a five-second startup stall.

Command-line tools that Speakeasy generates from an OpenAPI description now check string flags against the schema’s pattern and maxLength, according to the Speakeasy changelog entry for version 1.801.0, dated Oct. 7. A value that doesn’t conform is rejected as a validation_error (CLI_VALIDATION) with exit code 2.
Other flag behavior changed in the same release
Unknown-flag errors now suggest the closest flag name. --all pagination renders as one aligned table under --output-format table. --jq on a command that streams by default requests one complete response. Pass --stream or -o json to filter each streamed event.
A five-second startup stall is removed
Generated CLIs no longer query the terminal at startup. Speakeasy said that ends a five-second stall on pseudo-terminals. Keychain calls now time out after 2 seconds and fall back to the config file. Credentials passed by flag or environment variable skip the keychain, and --no-keyring turns it off.
Intent commands handle partial bodies and presets
Speakeasy introduced declarative intent commands on Sept. 14, declared through x-speakeasy-cli-commands. Version 1.801.0 lets an intent flag bind one level beneath an object preset, such as a field under $.format. Presets now fill missing keys in a partial object. A pinned union variant’s type discriminator is no longer dropped. Presets also merge into a piped stdin body. A body that names a different union variant is a validation error rather than being sent.
The release also shows delayed progress for synchronous terminal requests and rewrites the async polling progress line in place on an interactive terminal. Speakeasy also listed offline catalog defaults and validated enum groups.
Generators outside the CLI also changed
TypeScript and MCP TypeScript gained a numericEnumMemberNames option that spells _1 as One for new SDKs. Go and Terraform now return the last retryable response when the context deadline expires during a retry wait. Terraform providers no longer modify http.DefaultClient. Generated docs for Mintlify render emoji instead of GitHub shortcodes.
Key takeaways
- String flags enforce
patternandmaxLengthand fail with exit code 2. - A five-second startup stall on pseudo-terminals is removed.
- Keychain lookups time out after 2 seconds and fall back to the config file.
- Presets merge into piped bodies, and conflicting union variants are rejected.
The take
We think the CLI is the right place for schema checks. A script or an AI agent that runs a command gets a named error and an exit code it can read. That only helps if the schema is accurate. The checks will expose any pattern that was written loosely. Before regenerating, run the most-used commands against a test account and see which ones now fail. Then fix the schema, not the flag.


