Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
#533 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
716
Forks
132
Ø Merge
15 Std. 26 Min.
Gemergte PRs (30 T.)
208

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus existence-master/Sentient

Alle Issues in existence-master/Sentient

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.