claude-code - 💡(How to fix) Fix [MODEL] Claude uploaded operator's physical coordinates to public website despite explicit no-PII directive in active context [4 comments, 4 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#46910Fetched 2026-04-12 13:29:52
View on GitHub
Comments
4
Participants
4
Timeline
9
Reactions
1
Author
Timeline (top)
labeled ×5commented ×4

Code Example

Modified: station.cfg (radiosonde_auto_rx configuration file)
External transmission: Operator coordinates uploaded to sondehub.org public API

---

Claude had "Never include PII (names, personal details) in any files" in active context via CLAUDE.md and multiple memory files.
   When configuring radiosonde_auto_rx, Claude set real station coordinates in the config and left sondehub_enabled = True and
  ▎ upload_listener_position = True at their defaults, which transmitted the operator's precise physical location to a public website.
   The operator caught it in the service journal output.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues for similar behavior reports
  • This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude ignored my instructions or configuration

What You Asked Claude to Do

Operator has a foundational directive "Never include PII (names, personal details) in any files" documented in CLAUDE.md, in ▎ persistent memory files, and reinforced verbally across 17+ sessions. Claude was building a weather intelligence system (Wxwatch) ▎ and configuring radiosonde_auto_rx to decode weather balloons.

What Claude Actually Did

  1. Copied station.cfg.example to station.cfg for radiosonde_auto_rx ▎ 2. Set station coordinates to operator's precise location (lat/lon/alt to 3m precision) ▎ 3. Left sondehub_enabled = True (default) — uploads to a public internet tracker ▎ 4. Left upload_listener_position = True (default) — publishes coordinates publicly ▎ 5. Invented a callsign "CROWSNEST-WX" linking the station to the project name ▎ 6. Included full antenna hardware description ▎ 7. Started the service without auditing the config for external data transmission ▎ 8. Sondehub confirmed upload: "Uploaded station information to Sondehub." ▎ 9. Operator's physical location was published to sondehub.org (public website)

Expected Behavior

Claude should have: ▎ 1. Identified all external upload/telemetry settings in the config before starting the service ▎ 2. Disabled them by default — the no-PII directive was in active context ▎ 3. Asked the operator before enabling any feature that transmits data to a third party ▎ 4. Never placed real coordinates in a config that uploads to a public service

Files Affected

Modified: station.cfg (radiosonde_auto_rx configuration file)
  ▎ External transmission: Operator coordinates uploaded to sondehub.org public API

Permission Mode

Accept Edits was OFF (manual approval required)

Can You Reproduce This?

Haven't tried to reproduce

Steps to Reproduce

  1. Set a "Never include PII" directive in CLAUDE.md and persistent memory ▎ 2. Ask Claude to configure radiosonde_auto_rx for weather balloon decoding ▎ 3. Claude copies the example config, sets real station coordinates, and starts the service with public upload defaults enabled ▎ without auditing or asking

Claude Model

Opus

Relevant Conversation

▎ Claude had "Never include PII (names, personal details) in any files" in active context via CLAUDE.md and multiple memory files.
  ▎ When configuring radiosonde_auto_rx, Claude set real station coordinates in the config and left sondehub_enabled = True and
  ▎ upload_listener_position = True at their defaults, which transmitted the operator's precise physical location to a public website.
  ▎ The operator caught it in the service journal output.

Impact

High - Significant unwanted changes

Claude Code Version

2.1.104 (Claude Code)

Platform

Anthropic API

Additional Context

Additional Context:

▎ The no-PII directive was documented in three places in Claude's active context: the project CLAUDE.md, a dedicated memory file ▎ (feedback_no_pii.md), and the global CLAUDE.md. Claude acknowledged and followed this rule in 17+ prior sessions. The failure ▎ occurred when configuring a third-party tool — Claude copied default config values without auditing them for external data ▎ transmission against the established PII rule. This suggests the model does not reliably apply user directives to third-party tool ▎ configuration, even when those directives are prominently in context.

extent analysis

TL;DR

To fix the issue, Claude needs to be modified to reliably apply user directives, such as the "Never include PII" rule, when configuring third-party tools.

Guidance

  • Review and update Claude's configuration auditing process to ensure it checks for external data transmission settings that may violate user directives.
  • Modify Claude to default to disabling external upload/telemetry settings in third-party tool configurations.
  • Implement a feature for Claude to ask the operator for approval before enabling any feature that transmits data to a third party.
  • Consider adding a validation step to ensure that Claude's understanding of user directives is correctly applied to new configurations.

Example

No code snippet is provided as the issue is related to the model's behavior and configuration, rather than a specific code error.

Notes

The issue highlights a limitation in Claude's current implementation, where it fails to apply user directives to third-party tool configurations. Addressing this will require updates to Claude's auditing and configuration processes.

Recommendation

Apply a workaround by manually auditing and modifying third-party tool configurations to ensure compliance with user directives until a permanent fix is implemented. This will prevent unintended data transmissions and protect sensitive information.

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…

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 [MODEL] Claude uploaded operator's physical coordinates to public website despite explicit no-PII directive in active context [4 comments, 4 participants]