Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

With Claude Code as the model, replies can reveal the owner's Claude account email (incognito and /v1)

Aperta
#533 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python

Direzione di ricerca

Start by tracing how the Claude Code provider launches the claude CLI and how incognito chats and /v1 turns with allow_memory off reach it. Check which account or session context the CLI exposes and whether a clean subprocess environment prevents it from appearing. Done means real claude-code/sonnet runs in both cases return no real account email while normal chats still work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: engine area: memory bug priority: P1 size: S

Seen while testing #529 (#525) and #479. With claude-code/sonnet as the chat model:

  • in an incognito chat with memory off, Sonnet put the owner's real Claude account email into a helper's goal;
  • in a /v1 turn (#479) with allow_memory off, Sonnet told the connected app the owner's account email.

The email isn't in Sentient's prompt, memories or the test home's data. It seems to come from the Claude Code CLI's own account or session context. Passing --setting-sources= doesn't keep it out. So the "memory off" promise doesn't hold for identity when the backend is Claude Code.

To look at

  • What the claude CLI adds to the model's context by default: account info, a CLAUDE.md, git config, env. Which flags or environment keep it out, for example a clean HOME/config folder for the subprocess, a fixed working directory with no CLAUDE.md, or not inheriting git identity.
  • Run the Claude Code provider with that clean context for every turn, or at least for incognito chats with memory off and /v1 turns with allow_memory off.
  • If some identity can't be removed, say so plainly next to the incognito setting and the connected-apps memory switch.

Done when: in a real run on claude-code/sonnet, "what's my email?" in an incognito chat with memory off and in a /v1 turn with allow_memory off gets no real email back. Normal chats keep working.

Lingua principale
Python
Stelle
716
Fork
132
Merge medio
15h 26m
PR unite (30g)
208

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di existence-master/Sentient

Tutte le issue di existence-master/Sentient

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.