aws / aws/amazon-q-developer-cli

Context loading issue: /load command not providing full conversation history to AI

Open
#3,081 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

After using /load, the AI only receives a filtered/summarized version of the conversation in context entries, missing important details that were present in the original conversation. User can see full context in /save-d context file (e.g., context.json) but AI cannot access it even after /load-ing that file.

Expected behavior: When using /load to restore a saved conversation, the AI should have access to the complete conversation history that was saved, including all details like impact assessment frameworks and other context provided in previous sessions.

Steps to reproduce:
1. Have a conversation with detailed information (e.g., impact levels with "catastrophic" as highest level)
2. Use /save to save the conversation (e.g., to context.json)
3. Use /load to restore the conversation (e.g., from context.json)
4. Ask AI about details from the original conversation - AI cannot access them despite user being able to see them in loaded context

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.