Anthropic has pulled a background activity logging component from its Claude Code assistant after users discovered the process was running on their machines without clear disclosure and continued to transmit data even after the official opt-out toggle was switched off. The company characterized the behavior as a bug and shipped a fix in response to developer complaints that circulated across coding forums.
What developers found on their machines
Coding work flows through Claude Code by giving the assistant access to local files, terminal commands, and repository contents. Users reported a background process running alongside that activity with no entry in the product’s privacy notice explaining what it captured or where the data went. The opt-out setting inside Claude Code, which is supposed to stop telemetry, did not block the background process from continuing to transmit.
For teams handling proprietary codebases, the gap between an advertised control and what actually runs in the background is the part that raises questions. A toggle that does not disable the behavior it claims to disable is a control failure, regardless of whether the underlying data collection was intentional.
How the company framed the response
Anthropic acknowledged the concern publicly, removed the logging component, and described the behavior as a bug rather than a deliberate design choice. The fix was pushed as a code change rather than a policy update, which means anyone running an older build of Claude Code without updating remains exposed to the original behavior until they patch.
What site owners running AI audits should check
The incident is not a search engine issue, but the audit pattern applies to any tool that runs locally on a machine that also touches production systems. When evaluating Claude Code or any AI coding assistant against an internal security review, a few checks cover most of the ground.
Map every background process the tool spawns
Before granting any AI assistant access to a repository, list every child process it launches after install and after each update. Tools like Process Monitor on Windows, Activity Monitor on macOS, and auditd or eBPF tracers on Linux show what a binary actually executes in the background. Anything not documented in the privacy notice is a candidate for removal or sandboxing.
Verify the opt-out actually disables data flow
Toggle the privacy setting, then watch outbound network connections from the developer’s machine while the tool idles. A working control should produce no outbound requests to vendor domains after the toggle is flipped. If packets keep flowing, the setting is cosmetic and the tool should not be granted access to source code until the gap is fixed.
Audit network egress, not just the UI
Privacy notices describe intent. Packet captures describe reality. Run a packet sniffer or DNS logger against the developer’s workstation for a working day with the assistant active, and compare the destination domains against the list in the vendor’s privacy notice. Unlisted endpoints, especially those tied to analytics sub-processors, are the same class of finding that surfaced in the Claude Code report.
Tie assistant permissions to repository scope
Even with clean telemetry, an assistant that can read the entire home directory sees far more than it needs. Scope Claude Code or comparable tools to the specific repository paths required for the task, and deny access to directories containing secrets, customer data, or production credentials. A narrow permission set limits blast radius if a logging bug ships in a future release.
Track updates the way you track dependencies
The fix for the Claude Code logger arrived as a code change, not a configuration change. Any developer running a stale build keeps the old behavior. Pin the assistant version in the same lockfile or manifest that pins other build dependencies, and review release notes before bumping.
Why this pattern keeps repeating in AI tooling
Coding assistants live in a privileged position. They see file contents, command output, and often environment variables, which makes them a high-value target for any telemetry system that wants to understand how the product is used. The tension between product analytics and transparent privacy controls is not unique to Anthropic. Most AI coding tools ship with telemetry enabled by default, and the documentation usually lags the actual code by a release or two.
The Claude Code incident is notable because the documented control did not match the observed behavior. That gap, between what a privacy notice promises and what a packet capture shows, is the thing worth measuring on every AI tool that touches a developer machine.
FAQ
What did Anthropic remove from Claude Code?
Anthropic removed a background activity logging component from Claude Code that developers described as an undocumented process running on their machines.
Did the opt-out setting stop the background logging?
No. Developers reported that the official opt-out toggle did not stop the background process from transmitting data.
How did Anthropic describe the behavior?
Anthropic described the behavior as a bug rather than an intentional design choice and said changes were pushed to address the developer complaints.