{"version":"2.1.290","anchor":"plugin-command-timeout-ceiling-is-now-a-constant","canonical_anchor":"plugin-command-timeout-ceiling-is-now-a-constant","heading":"Plugin command timeout maximum is now set elsewhere","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/plugin-command-timeout-ceiling-is-now-a-constant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Plugin command timeout maximum is now set elsewhere\n\nThe maximum timeout for a plugin command is no longer written as 600 seconds, and the default is still 60\n\n**Unclear.** Whether the maximum is still 600 seconds is not clear.\n\n**What**\n\nA plugin command can say how many seconds Claude Code should wait for it before giving up. The highest allowed value used to be written directly as 600. It now comes from a value defined elsewhere in Claude Code. The description still gives the default as 60 seconds.\n\n**Why**\n\nThe longest timeout a plugin command can ask for may be different now.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}