DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
Settings rows hide when the value is set outside your user settings
You'll notice
Useful2Signal2
Settings
The question auto-continue timeout row disappears when its value is set by policy rather than by you.
What's wrong with this entry?
Anonymous. No account, no email.
What
The "Question auto-continue timeout" row is now hidden whenever its effective value comes from somewhere other than your own user settings, so a managed or policy-set value no longer appears as an editable field.
Details
The row is consent-gated, and a failed save now restores the previous value in the panel rather than leaving the new one displayed.
Evidence
Question auto-continue timeout
Strings lifted out of the shipped bundle, so the claim above can be checked against them.