{"version":"2.1.311","anchor":"remote-control-long-lived-token-message-and-startup-tuning","canonical_anchor":"remote-control-long-lived-token-message-and-startup-tuning","heading":"Small changes to remote control errors, startup and permission prompts","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remote-control-long-lived-token-message-and-startup-tuning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Small changes to remote control errors, startup and permission prompts\n\nA clearer token error for remote control, extra startup measurements, and permission prompts that can show a note from the tool\n\n**What**\n\nA few small changes:\n\n- When a long-lived token, a saved login that stays valid for a long time, does not have the access remote control needs, the error message now comes from a shared helper.\n\n- At startup, Claude Code now records process tuning details and starts counting garbage collections, which are runs of the program's automatic memory cleanup.\n\n- Permission prompts, which ask whether Claude may use a tool, can now show a note supplied by that tool.\n\n**Why**\n\nThese are minor changes. The most visible one is that some permission prompts may now carry an extra note.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}