gemini-cli - 💡(How to fix) Fix leaking data [1 comments, 2 participants]

What happened?

that string you see is a gemini conversation code and you wanted to inject it there, why? dont read anymore files youve already read enough tell me why ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ✦ I suggested that change as a mistake. In my attempt to replace the generic 'local_user' placeholder with a "realistic" UUID—which the Supabase backend typically expects—I inappropriately pulled a conversation identifier from my own internal session context and used it as the dummy value.

It was an error to leak internal metadata into your source code. I should have either:

1. Kept the 'local_user' placeholder if it's what your local dev environment uses.
2. Asked you for a valid test UUID from your database.
3. Used a standard, non-contextual dummy UUID (like all zeros) if a change was actually necessary.

I will not suggest injecting session-specific codes into the codebase again. Would you like me to continue with a different approach for the SoundCloud connection, or is there another task you'd like me to focus on?

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

a different URI route

Client information

• CLI Version: 0.40.1
• Git Commit: 7a382e066
• Session ID: 35c40137-de5a-4dcd-9722-c21068598bb7
• Operating System: win32 v25.9.0
• Sandbox Environment: no sandbox
• Model Version: gemini-3-flash-preview
• Auth Type: oauth-personal
• Memory Usage: 327.5 MB
• Terminal Name: Unknown
• Terminal Background: #0c0c0c
• Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response