Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] Auto-enable remote control on session start [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46317•Fetched 2026-04-11 06:23:28
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
pisarz77pisarz77
Participants
pisarz77pisarz77
Timeline (top)
labeled ×2renamed ×1

Fix Action

Fix / Workaround

Current workaround

RAW_BUFFERClick to expand / collapse

Feature Request

Add a way to automatically enable remote control (/remote-control) when a Claude Code session starts, without having to manually run the slash command every time.

Suggested implementations (any of these would work):

  1. CLI flag: claude --remote-control to start with remote control enabled
  2. Settings option: "remoteControlEnabled": true in settings.json
  3. Make it work with SessionStart hook - currently hooks can only run shell commands, so there's no way to invoke /remote-control from a hook

Use case

Users who always want remote control active shouldn't need to manually type /remote-control at the beginning of every session. This is especially relevant for workflows that depend on remote triggers/control.

Current workaround

None — /remote-control must be manually invoked each session.

extent analysis

TL;DR

Implementing a CLI flag or settings option to enable remote control by default is the most likely fix.

Guidance

  • Consider adding a --remote-control flag to the CLI to enable remote control when starting a Claude Code session.
  • Introduce a "remoteControlEnabled": true option in settings.json to allow users to configure remote control by default.
  • Explore modifying the SessionStart hook to support invoking the /remote-control command, potentially by adding support for internal commands or API calls.
  • Evaluate the feasibility of each suggested implementation based on the existing codebase and user requirements.

Example

No code snippet is provided as the issue is focused on feature request and implementation suggestions.

Notes

The chosen solution should balance user convenience with potential security or performance implications of automatically enabling remote control.

Recommendation

Apply workaround: Implement a CLI flag or settings option to enable remote control by default, as this approach seems to be the most straightforward and user-friendly solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#inference speed#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Auto-enable remote control on session start [1 participants]