{"version":"2.1.319","anchor":"remote-control-prompts-handle-non-interactive-stdin","canonical_anchor":"remote-control-prompts-handle-non-interactive-stdin","heading":"Remote Control setup exits with advice when it cannot read your answer","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/remote-control-prompts-handle-non-interactive-stdin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Remote Control setup exits with advice when it cannot read your answer\n\nIf `claude remote-control` cannot read a reply to its setup questions, it now exits and tells you to run it in a terminal\n\n**What**\n\n`claude remote-control` turns on Remote Control. It asks \"Enable Remote Control? (y\/n)\" and \"Choose [1\/2] (default: 1):\" and waits for your answer. These questions are now asked in a different way.\n\nIf Claude Code cannot read an answer, the command now exits with this message: \"Run `claude remote-control` at a terminal and answer y once; it won't ask again.\" This can happen when the command runs from a script or in the background.\n\n**Why**\n\nRunning the command from a script or in the background now ends with a clear message instead of waiting forever for an answer.\n\n- Area: Remote Control\n- Names: `claude remote-control`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}