You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
squad_decide MCP tool rejects author values that contain spaces, parentheses, or other characters needed to attach role context. The validator only accepts [A-Za-z0-9_-]+. This makes it impossible to express authorship like "Squad (Coordinator) on behalf of Tamir Dresher (CTO)" — which is the most accurate description for structural decisions made by the coordinator on behalf of a human directing the work.
Reproduction
Tested on @bradygaster/squad-cli@0.10.0-build.7 (local build from PR #1245 branch).
mcp_call({tool: "squad_state-squad_decide",args: {author: "Squad (Coordinator) on behalf of Tamir Dresher (CTO)",summary: "...",body: "..."}});
Returns:
MCP server 'squad_state': Invalid author name: must contain only letters,
numbers, hyphens, and underscores
Why this is too narrow
The author field on a decision is human-readable provenance. Real authorship in a multi-agent system is often complex:
"squad-coordinator" — accepted today, but loses the "on behalf of" context
"Scribe on behalf of Flight" — rejected, contains spaces
Workaround today is to embed the full attribution in the body and put a slug in author. But that defeats the purpose of having an author field — automated tooling that displays decisions by author cannot show the real authorship.
Reject only characters that would break filename derivation (the slug is derived from this in the inbox filename)
Or split into two fields: author_slug (the strict validator, used for the filename) and author_display (free text, used for the human-readable header).
Activity
fix(sdk): address Copilot review — reject empty author slug, report r…
fix(sdk): allow identity/* state writes and widen squad_decide author…
chore(release): prepare v0.12.0
chore(release): prepare v0.12.0 (#1691)
chore: promote dev -> main (v0.12.0) (#1698)