Claude Code 2.1.132: Multiagent docs, schedule gate, skill limit changes

Release v2.1.132 of the Claude Code system prompts (tagged by the Piebald-AI repo) ships several documentation expansions, a new system prompt gate, and a skill-limit correction.

Key changes

• Managed Agents documentation: New reference docs for multiagent sessions (coordinator rosters, per-agent threads, thread endpoints/streams, multiagent events, subagent tool permissions), outcomes (user.define_outcome rubric-graded loops, evaluation events, deliverables, interrupts), and webhooks (HMAC verification, payload envelopes, event types, retries, delivery behavior).
• Schedule offer gate: A new system prompt (Strict proactive schedule offer gate) defaults to deny for proactive /schedule offers. It requires a named future-obligation artifact, concrete timing, and no in-session follow-up path. Proactive scheduling instructions were removed from the schedule tool description.
• Skill limit update: The documented Managed Agents skill limit dropped from 64 to 20 per agent across multiple prompt sections (onboarding flow, core concepts, tools and skills).
• Security monitor expansion: The autonomous agent security monitor now allows CronCreate, CronDelete, CronList, and RemoteTrigger actions for managing Claude Code tasks.
• Prompt Suggestion Generator v2: Added a safety rule to stay silent when suggestions could predict unsafe or sensitive actions (including legitimate security work).
• Status line clarification: Input tokens reflect current context-window tokens (including cache reads/writes); output tokens are from the most recent API response.
• Future follow-up rules: A new system prompt defines future follow-ups as work more than two hours out or unavailable in-session, lowers the confidence threshold to 75%, and preserves concrete one-time/recurring scheduling signals.

Impact

If you use Managed Agents, update your agent configurations to respect the new 20-skill limit. The schedule gate will affect any workflow relying on proactive /schedule offers — expect the agent to require explicit future obligations before suggesting scheduling. Multiagent documentation is now live, covering endpoints, events, and webhooks for deeper integration.