aws / aws/amazon-q-developer-cli

Cannot list saved conversations to load

オープン
#3,147 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

Feature request q chat
主要言語
Rust
スター
2k
フォーク
439
PR マージ指標
30日以内にマージされた PR はありません

説明

Checks
Operating system

macOS 15.7.0 (24G222)

Expected behaviour

I previously used "/save" on a conversation, but I do not recall what name I have it. The system keeps saying that I can use "/load" with parameters to list saved conversations, but then gives an error when I try that. If it cannot list what is saved, then saving does not help much.

Actual behaviour

🤖 You are chatting with claude-sonnet-4

how does /save work

🛠️ Using tool: introspect (trusted)

● Introspecting to get you the right information

● Completed in 0.1s

The /save command saves your current conversation to local storage so you can resume it later.

Basic usage:
• /save - Saves the conversation with an auto-generated name
• /save - Saves the conversation with a specific name you provide

Loading saved conversations:
• /load - Shows a list of saved conversations to choose from and loads the selected one

Storage location:
Conversations are saved locally in your file system and persist across Q CLI sessions.

Example:

/save my-project-discussion
Conversation saved as "my-project-discussion"

/load
? Select a conversation to load:
❯ my-project-discussion
previous-chat-session
debugging-help

The save/load functionality lets you maintain multiple ongoing conversations and switch between them as needed.

Reference: https://github.com/aws/amazon-q-developer-cli/blob/main/README.md

"/load" by itself does not do this: "Shows a list of saved conversations to choose from and loads the selected one" it only gives error

You're correct. I apologize for the inaccuracy in my previous response.

Looking at the documentation, I can see that /save and /load commands are listed in the built-in help, but the specific behavior of /load when used without
arguments is not documented in the available Q CLI documentation.

The documentation only confirms that:
• /save - Save the current conversation
• /load - Load a previous conversation

The exact interface and behavior of /load when used alone (whether it shows an interactive list, requires arguments, or gives an error) is not specified in the
available documentation.

Reference: https://github.com/aws/amazon-q-developer-cli/blob/main/README.md

so where did you get this example from: "
/load
? Select a conversation to load:
❯ my-project-discussion
previous-chat-session
debugging-help"

You're absolutely right to call that out. I generated that example based on assumptions about how the /load command might work, rather than from the actual Q CLI
documentation.

The documentation I have access to only lists /load as "Load a previous conversation" without providing any details about its specific behavior, interface, or
examples.

I should not have created that fictional example. The correct response is that the specific behavior and usage of /load is not documented in the available Q CLI
documentation.

Steps to reproduce

/save xxx
/quit

q chat
/load

error: the following required arguments were not provided:

Environment
[q-details]
version = "1.16.1"
hash = "dad39a19a27fba493d42acb53972d5c721fa1081"
date = "2025-09-17T19:53:46.980195Z (23d ago)"
variant = "full"

[system-info]
os = "macOS 15.7.0 (24G222)"
chip = "Apple M1 Pro"
total-cores = 10
memory = "16.00 GB"

[environment]
cwd = "/Users/USER/.aws/amazonq/history"
cli-path = "/Users/USER/.aws/amazonq/history"
os = "Mac"
shell-path = "/bin/bash"
shell-version = "3.2.57"
terminal = "iTerm 2"
install-method = "unknown"

[env-vars]
PATH = "/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Users/USER/.local/bin:/Users/USER/.krew/bin:/usr/local/bin:/opt/homebrew/bin:/Users/USER/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/homebrew/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin"
QTERM_SESSION_ID = "735c4c1e21344e8c9eca16bf86426655"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.16.1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

調査の方向性

q chat で、ドキュメントに記載された手順を再現することから始めます: /save xxx、/quit、q chat を再起動し、その後 /load を実行します。/load コマンドの処理と、必須の PATH 引数を追跡します。/load をパスなしで呼び出したときに、ユーザーが保存済みの会話を一覧表示して選択でき、報告されたエラーもカバレッジに含まれていれば完了です。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
rust
領域
cli
issue の種類
バグ
難易度
3/5
見積もり時間
1〜2日
活発さ
停滞
明瞭さ
おおむね明確
初心者へのやさしさ
38/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。