Skip to content

fix: require explicit consent for Entire session tracking - #39

Closed
Tomeriko96 wants to merge 1 commit into
mainfrom
fix/entire-consent
Closed

Tomeriko96 wants to merge 1 commit into
mainfrom
fix/entire-consent

Conversation

@Tomeriko96

Copy link
Copy Markdown

Problem

claude() alias auto-enables Entire with entire enable -y, uploading session transcripts (prompts, tool output, responses) to cedanl/entire-checkpoints without user acknowledgment.

Session data includes:

  • User prompts (containing business logic, code, strategies)
  • Tool output (file contents, API responses, credentials in rare cases)
  • Assistant responses
  • Repository details

GDPR Issue: Automatic tracking without explicit per-session consent violates privacy regulations (GDPR Art. 7).

Solution

Replace auto-enable with:

  1. Prominent notice — displayed on first claude() invocation in repo
  2. Explicit opt-in — user must run entire enable --agent claude-code
  3. Clear labeling — COMPLIANCE note explaining data handling

Implementation

  • Removes entire enable -y (was auto-enabling)
  • Removes entire configure (now manual)
  • Adds check: only notify if Entire is available but not enabled
  • Shows 3-line notice with link to enable/configure

Behavior After Fix

User runs claude for first time in repo:

Subsequent runs: Claude starts normally (user chose).

Compliance

✓ GDPR Art. 7 — explicit, freely given, informed consent
✓ Privacy by design — notice + opt-in, not opt-out
✓ Transparency — data destination and content clearly documented
✓ User control — users can disable, switch remotes, or skip

Note: onboard.sh already prompts for Entire consent at setup. This ensures the claude() alias respects that choice (no override).

Closes #24.

🤖 Generated with Claude Code

COMPLIANCE: claude() alias previously auto-enabled Entire with -y flag,
uploading session transcripts (prompts, responses, tool output) to
cedanl/entire-checkpoints without user acknowledgment.

Changes:
- Remove auto-enable (entire enable -y)
- Display prominent notice on first run (per-repo, per-agent)
- Require explicit manual opt-in: entire enable --agent claude-code
- Add GDPR compliance comment explaining data handling

Users now have clear choice:
✓ Enable: entire enable --agent claude-code
✓ Configure: entire configure --checkpoint-remote ...
✗ Disable: unset ENTIRE_AGENT_NAME or ignore prompt

Note: onboard.sh already asks for Entire consent. This ensures the
claude() alias also respects user preference (not forcing auto-enable).

Fixes issue #24 (GDPR/explicit consent).
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Entire-Checkpoint: ae286217ffdc
@Tomeriko96 Tomeriko96 closed this Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🟠 security: entire-upload zonder expliciete toestemming

1 participant