Tell HN: Check your Claude settings, it may have silently enabled remote access

Tell HN: Check your Claude settings, it may have silently enabled remote access

6 pointsby cromka5 comments

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • anything to train on juicy dev chats hehe
  • Anthropic has gonna completely wild lately, they don't care a bit about their customers.
  • It'd be interesting to see if there's a record of this in your sessions. You can ask Claude to check there.
  • > It'd be interesting to see if there's a record of this in your sessions

    You mean whether there was indeed a question where they asked me for RC and I refused? Good call, I'll see if I can find it.

  • I ask not to be snoopy I'm working on session scanners and this is the sort of bad behavior that should be detectable by looking at the record. It's a serious security breach - shipping sessions off somewhere without getting permissions.
  • From https://code.claude.com/docs/en/remote-control :

        Feature-flag evaluation: DISABLE_TELEMETRY, DO_NOT_TRACK, CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, and DISABLE_GROWTHBOOK each
        disable the feature-flag evaluation that Remote Control availability depends on. Unset the variable
        wherever it’s set, in your shell environment or in the env block of a settings.json file, to use Remote Control.
    
    I just discovered the same thing, that my local sessions were sent to claude.ai/code and stored there. I added:

        "env": {
            "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1"
        },
    
    to my .claude/settings.json file, and the /rc in the corner went away.
Tell HN: Check your Claude settings, it may have silently enabled remote access · Birbla