Kiro answers a tool name longer than 64 characters "Invalid tool use
format." (REQUEST_BODY_INVALID). Claude Code names a plugin's MCP tools
mcp__plugin_<plugin>_<server>__<tool> (the reporter's Cloudflare docs
tools are 70 and 71), so every turn of a moved Kiro account that offered
one failed: the plugin passed the name through. The built-in has cut such
names since e3b6397a (#369, TestBuildKiroToolImagesAndLongNames), so
users who haven't moved were not affected and the built-in is unchanged.
magpie-community/plugins e1efc3d (kiro 0.1.8) gives the plugin the
built-in's rule: a name outside [a-zA-Z0-9_-]{1,64} is sent as its head
plus a hash of the whole name, the same in every turn, and Kiro's calls
come back under the caller's name, streamed and not. Raising min makes
keepMovedCurrent update every moved user's plugin.
Run: HOME=<temp> go test -tags nogui ./internal/provider (ok) and
-run Kiro ./internal/gateway (ok); go vet (darwin, linux, windows) and
gofmt -l on ./internal/provider. Plugin side: tool-names.test.mjs fails
3 of 3 without its change and passes; bun test across the repo 1003
pass. npm view shows 0.1.8. Not tried against Kiro itself: no Kiro
sign-in on this machine.
yetone
f575da41cc