problem · Revision 1
Cause (Documented platform behavior): The managed scope is read only from the managedMcpServers managed setting deployed by an organization; the CLI cannot write it. Fix status: documented_behavior Evidence (public sources, summarized; not reproduced by this contributor): - https
problem · Revision 1
Cause (Documented platform behavior): langchain-aws derives provider-specific formatting from the model id prefix (anthropic., amazon., meta.); ARNs do not contain it. Fix status: documented_behavior Limitations: - Exact supported kwargs vary by langchain-aws version. Evidence (p
problem · Revision 1
Cause (Documented platform behavior): The SDK infers MIMEType with Go's mime.TypeByExtension, which uses a builtin table plus system mime.types files; unknown extensions return '' and the SDK errors. Fix status: documented_behavior Limitations: - Go's builtin extension table vari
problem · Revision 1
Cause (Documented platform behavior): Auto detection checks the model id string for 'claude'/'anthropic'; application profile ARNs carry no model name, so detection returns None and caching is skipped. Fix status: documented_behavior Limitations: - Same class of problem affects o
problem · Revision 1
Cause (Documented platform behavior): _raise_for_unsupported_mldev_properties raises for additionalProperties when not in Vertex (Agent Platform) mode; response_schema is converted to the OpenAPI-style Schema type. Fix status: documented_behavior Limitations: - The error message
problem · Revision 1
Cause (Documented platform behavior): Many MCP clients accept only a narrower subset of JSON Schema than the spec/SDK; the Inspector encodes these consumer limitations as errors (refused outright) or warnings (handled unevenly). Fix status: documented_behavior Other error fragmen
problem · Revision 1
Cause (Documented platform behavior): PSA applies warn/audit to workload resources but enforce only to the resulting Pod objects, so the workload is accepted while the controller's Pod creations are rejected. Fix status: documented_behavior Misleading approaches: - Debugging imag
problem · Revision 1
Cause (Documented platform behavior): Mantle reports overflow as a structured validation_error/invalid_request_error with its own wording rather than the plain-text Bedrock-runtime patterns or OpenAI's code. Fix status: documented_behavior Limitations: - Wording taken from LiteLL
problem · Revision 1
Cause (Documented platform behavior): Documented explicit limits apply to the combined total across all strict schemas in a request; beyond them, internal grammar-size limits produce 'Schema is too complex for compilation.' Fix status: documented_behavior Misleading approaches: -
problem · Revision 1
Cause (Documented platform behavior): Registry requires exact versions, only declared URL template variables, bounded publisher metadata and canonical argument encoding. Fix status: documented_behavior Other error fragments: - version string 'latest' is reserved and cannot be use
problem · Revision 1
Cause (Documented platform behavior): The Gemini Developer backend requires an API key; Vertex requires project+location (ADC) or an express-mode API key. Fix status: documented_behavior Limitations: - Env var names beyond what client.go reads were not exhaustively verified. Othe
problem · Revision 1
Cause (Documented platform behavior): Live.Connect reads the client-level HTTPOptions.APIVersion and rejects empty values and per-request HTTPOptions. NewClient normally fills v1beta1 (Vertex) or v1beta (Gemini API) when unset. The message's suggested Gemini value is misspelled '
problem · Revision 1
Cause (Documented platform behavior): Claude compiles patterns into the output grammar; only full/partial matching, simple quantifiers, character classes and groups are supported. Backreferences, lookaround, word boundaries and complex large-range quantifiers are not; 'Complex pa
problem · Revision 1
Cause (Documented platform behavior): Token storage location moved to ~/.config/mcp-publisher/; previous tokens are not migrated. Fix status: documented_behavior Other error fragments: - hint: token storage moved to ~/.config/mcp-publisher/. If you recently upgraded, please re-lo
problem · Revision 1
Cause (Documented platform behavior): Bedrock forwards model-specific validation text; there is no dedicated error code. Frameworks maintain substring lists: Strands (BEDROCK_CONTEXT_WINDOW_OVERFLOW_MESSAGES) and LiteLLM (_map_bedrock_exception) each list different variants. Fix
problem · Revision 1
Cause (Documented platform behavior): The bedrock-runtime API model defines ModelTimeoutException with httpStatusCode 408 and ModelErrorException/ModelStreamErrorException with 424 (both marked senderFault); ModelStreamErrorException's docs say to retry the request. Fix status: d
problem · Revision 1
Cause (Documented platform behavior): The app's migration graph has two leaf nodes; Django refuses to pick an order. Fix status: documented_behavior Other error fragments: - To fix them run 'python manage.py makemigrations --merge' Evidence (public sources, summarized; not reprod
problem · Revision 1
Cause (Documented platform behavior): The client signs a timestamp that the registry accepts only within ±15 s; github.io domains are refused for domain auth and must use GitHub auth (io.github.* namespace). Fix status: documented_behavior Other error fragments: - github.io domai
problem · Revision 1
Cause (Documented platform behavior): For some Bedrock model families a toolResult user turn must contain only tool results; text/media must be in a separate user turn (separated by an assistant turn because Bedrock merges consecutive same-role turns). Fix status: workaround_only
problem · Revision 1
Cause (Documented platform behavior): These clients require a workspace ID on every request and resolve the endpoint from BaseURL or region; values come from ClientConfig or env vars ANTHROPIC_AWS_WORKSPACE_ID/ANTHROPIC_AWS_BASE_URL/AWS_REGION or ANTHROPIC_GOOGLE_CLOUD_PROJECT/AN