{"version":"2.1.224","anchor":"new-setting-dialogexpiry","canonical_anchor":"new-setting-dialogexpiry","heading":"New setting: dialogExpiry","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/new-setting-dialogexpiry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### New setting: `dialogExpiry`\n\ndialogExpiry accepts 60s, 5m, 10m or never for how long forwarded dialogs and held messages wait.\n\n**What**\n\nA new settings key controls how long a permission or question dialog forwarded to a remote client stays parked, and how long a held cross-session message waits for approval, before resolving to its safe no-action default. Accepts \"60s\", \"5m\", \"10m\" or \"never\", defaults to 5 minutes, and falls back to the default on an invalid value. Purely local prompts are unaffected.\n\n**Details**\n\n- Resolution order: the environment variable `CLAUDE_CODE_USER_DIALOG_TIMEOUT_MS`, then `dialogExpiry`, then 300000 ms.\n- Read from trusted settings sources only, and sits next to the existing `askUserQuestionTimeout` key with the same enum.\n\n**Usage**\n\n`{ \"dialogExpiry\": \"10m\" }` **Evidence** `dialogExpiry: Ir([\"60s\", \"5m\", \"10m\", \"never\"])`, `dialogExpiry`\n\n- Area: Permissions\n- Names: `dialogExpiry`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}