"env": {
    "CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY": "1",
    "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1",
    "DISABLE_AUTOUPDATER": "1",
    "IS_DEMO": "1"
  }

You CAN set these as env vars in your shell, but I prefer to stick 'em in the Claude settings.json:

  $ cat ~/.claude/settings.json
  {
    "env": {
      "CLAUDE_CODE_DISABLE_TERMINAL_TITLE": "1",
      "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1"
    }
  }

In that I pointed out that they are sending data back that shouldn't be and is not in compliance with their stated data usage policy [3]. Specifically, message ids which have no purpose other than to link surveys to chat history and this was being sent even when disabled (at the time. I haven't dug into the code since).

[1] https://github.com/anthropics/claude-code/issues/8036 [2] https://news.ycombinator.com/item?id=45838297 [3] https://code.claude.com/docs/en/data-usage

while you're here, would you generously allocate a couple minutes to assess this other issue? https://github.com/anthropics/claude-code/issues/4034

It's low-hanging fruit.

Thanks for talking to this community.

Claude Code is a very serious tool - in my opinion the only one of its kind suitable as a daily driver.

Without it my startup would grind to a halt. It’s akin to a delivery business needing its fleet of delivery vans.

Every time Claude Code changes we get nervous. Will the few humans who steward this product keep us in mind? Will we be forced to invent our own workflow?

All we want is for our reliable delivery van to keep delivering.

Appreciate you for reading and keeping us in mind as you evolve the product.