Resume the conversation. Keep the old credentials too?

Description and use

When saving an AI assistant session, old launch credentials may be persisted. The new logic removes them on save and injects current credentials on resume, preserving conversation history.

Problem

When an AI assistant is resumed, the saved conversation may still contain old launch credentials, potentially exposing them or causing confusion about which credentials are active.

Outcome

The experiment confirmed that the new save/load logic preserves conversation history while preventing old launch credentials from being persisted. Legacy files remain unchanged until explicitly resaved, and the old credentials are not revoked by deletion.

Workflow

• 1. Launch assistant with environment variables (including credentials).
• 2. Save session – old logic writes full environment to disk.
• 3. Resume session – old logic loads old credentials from disk.
• 4. New logic: on save, strip env field; on load, inject current env.
• 5. Verify that conversation history is intact and that the file no longer contains old credentials.
• 6. Confirm that reading a legacy file does not rewrite it; only a subsequent save removes the old env.
• 7. Identify responsibilities for legacy files and backups.

Evidence

Our real-file experiment showed an easily missed state: resume used the current value while the old value remained in the file on disk.

Source

Reading and changing a file are separate operations.

Source