You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Bug FixesKind: in v2.1.309,
ImprovementsSection of the release
What
Before Claude Code starts sessions in a folder for Remote Control (claude rc, which lets you drive Claude Code from your other devices), it asks whether you trust that folder. That prompt and its error were written only for Remote Control. They are now built from a description of the feature, its name, its command, its wording and what to do when nobody is there to answer (unattendedRemedy), so other commands can reuse them.
The workspace-not-trusted error now says Run `<command>` again with the command that was actually used. It always said claude rc before.
The prompt no longer always says "Remote Control did not start"; its wording comes from the feature using it. For Remote Control it reads "Remote Control starts Claude Code sessions in this folder, driven from your other devices:".
The prompt accepts an optional timeout. If nobody answers in time it stops with "No answer in time." Before, there was no timeout.
A related internal step (j5e) can now be cancelled.
Why
The hint in the error now matches the command you ran, and a launch with nobody at the keyboard can end with a clear message instead of waiting on the trust question indefinitely.
