dsh-llm-kiro

LIMITATIONS

Known limitations

- **Coarse token usage.** Kiro reports only the percentage of the context window a request consumed, so the emitted `usage` chunk carries the derived input count and a zero output count: pressure tracking is accurate, billing-style breakdowns are not. - **No image input.** Image content is refused with `UNSUPPORTED_CONTENT` rather than silently flattened, though the wire operation does accept images. - **Tool names must match `^[A-Za-z][A-Za-z0-9_]{0,63}$`.** A name that does not is aliased by replacing every illegal character with `_` (so `mcp__a-b__c-d` goes on the wire as `mcp__a_b__c_d`) and reversed before dispatch; only a name no alias can rescue (empty, over-long, or not starting with a letter) is refused with `UNSUPPORTED_TOOL_NAME`. Two names that alias to the same wire name in one turn collide, last one wins. - **SOCKS proxies are unsupported.** Only `http://` and `https://` egress; a SOCKS proxy would need a dependency this package avoids. - **Thinking effort is a prompt marker, not a request field.** The budgets are fixed per effort level and the service may ignore them. - **The shipped model catalog reflects one verified account tier.** Another tier may serve more or fewer ids; the catalog is advisory and unlisted ids pass through.