Unclear Whether a built-in waiting time of 0 leaves this off unless it is set remotely is not confirmed.
A permission request is the prompt where Claude Code asks you to allow an action. In a remote session, which runs on a server rather than on your own computer, Claude Code can now decline such a request when nobody answers it. This happens only after the session has been held on the server long enough and the request has waited long enough. Claude then gets the message: "Nobody answered this permission request; the person may be away. Do not retry the call."
The waiting time comes from a server setting whose built-in value is 0, and Claude Code only acts after it has fresh values from the server.
A remote session left alone no longer stalls forever on a question nobody is there to answer. If you step away, you may come back to find a request was declined rather than still waiting.
tengu_misty_aurora Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.292: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.292. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Whether a built-in waiting time of 0 leaves this off unless it is set remotely is not confirmed.
New in this build: tengu_misty_aurora