Skip to content

/chat new command fails with "Session not found: new" in TUI mode (v1.28.1) #6771

@BSwansonAW

Description

@BSwansonAW

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 new for 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

  1. Start kiro-cli in TUI mode (kiro-cli --tui or with chat.ui set to "tui")
  2. Type /chat new in the chat input
  3. 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 --help does not list new as a subcommand or option
  • The slash commands documentation does not appear to document /chat new yet

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions