Remote-control tool calls: permission asks survive restarts and can offer session-only rules

What

With remote control, your machine runs tools on behalf of a session hosted elsewhere. How these tool calls and their permission prompts work has changed. A permission prompt is the question Claude Code asks before running a tool.

• The call path gains earlyCheckTiming, reconnectHoldMs and pendingAsk settings, a standing-line status, and a check before sending that reports whether the call was accepted (onAccepted/onNoRecord).
• A permission ask that was still waiting when Claude Code restarted now carries over. It skips the first permission check and tells the prompt it was pending before the restart (pendingBeforeRestart: true).
• Prompts now carry offeredStandingRules. When a tool's input is exactly a string and a rule is offered for that tool, the "always allow" suggestion adds that allow rule for the current session only (destination "session"). Otherwise it falls back to the old suggestion: a rule saved to local settings using the trimmed string, which refused empty strings and strings containing *.

Why

A pending permission question is less likely to be lost when a connection drops or Claude Code restarts. In some prompts, choosing "always allow" now gives a narrower permission that lasts only for the session instead of being saved to your settings.