generated from amazon-archives/__template_Custom
-
Notifications
You must be signed in to change notification settings - Fork 187
Open
Labels
chatclipending-maintainer-responseIssue is pending a response from the Kiro teamIssue is pending a response from the Kiro teampending-triageui
Description
Before opening, please confirm:
Operating System
WSL2 (Ubuntu) on Windows
Kiro Version
1.28.1
Bug Description
The /chat new slash command was announced in the 1.28.0 changelog as a way to start fresh conversations without restarting the CLI:
You also get
/chat newfor starting fresh conversations without restarting the CLI
However, running /chat new in TUI mode produces the following error in red text:
Failed to start session: Session not found: new
It appears the /chat command handler is interpreting new as a session ID rather than recognizing it as a subcommand.
Steps to Reproduce
- Start kiro-cli in TUI mode (
kiro-cli --tuior withchat.uiset to"tui") - Type
/chat newin the chat input - Observe the error:
Failed to start session: Session not found: new
Also tested:
- Different working directories — same error
- Separate fresh session — same error
Expected Behavior
/chat new should start a fresh conversation session within the current CLI instance, as described in the 1.28.0 changelog.
Conversation ID
N/A — error occurs before a new session is created
Additional Context
- The classic (legacy) UI also does not recognize
/chat new kiro-cli chat --helpdoes not listnewas a subcommand or option- The slash commands documentation does not appear to document
/chat newyet
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
chatclipending-maintainer-responseIssue is pending a response from the Kiro teamIssue is pending a response from the Kiro teampending-triageui