Skip to content

[Bug]: /new, /clear, and /reset commands freeze the terminal session #33961

Closed as not planned

Description

@daniij

Bug Description

When attempting to use the slash commands /new, /clear, or /reset, the terminal interface completely freezes.

Upon pressing Enter, the cursor stops blinking, and the input field hangs, making it impossible to type anything. Standard interrupt shortcuts like Ctrl + C do not cancel the operation or return control to the user. The only way to recover is to completely close the terminal window and restart the program.

This bug happens regardless of the chat history: it occurs whether you have sent multiple messages, just one message, or if you run the command immediately upon launching the application without sending any text at all.

Image

Steps to Reproduce

  1. Start hermes-agent.
  2. Type and execute /clear (or /new / /reset). Note: This happens both immediately on a fresh launch or after any number of exchanged messages — history size does not affect the outcome.
  3. Notice that the command line freezes: the cursor stops blinking, and you can no longer type anything.
  4. Try pressing Ctrl + C to interrupt — notice it has no effect.

Expected Behavior

The command should execute successfully (clearing the screen or resetting the session ID and history) and immediately return an active, usable prompt with a blinking cursor, without requiring a hard restart of the console.

Actual Behavior

The application completely locks up. The cursor stops blinking, typing becomes completely disabled, and Ctrl + C fails to break or interrupt the process. The user is forced to kill the terminal session and launch the agent again from scratch.

Affected Component

CLI (interactive chat)

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

Report       https://paste.rs/cBHbT
agent.log    https://paste.rs/Ohf0t
gateway.log  https://paste.rs/voudq

Operating System

Windows 11

Python Version

3.11.15

Hermes Version

v0.14.0 (2026.5.16)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

Activity

  1. added
    type/bugSomething isn't working
    comp/cliCLI entry point, hermes_cli/, setup wizard
    P2Medium — degraded but workaround exists
    duplicateThis issue or pull request already exists
    on May 28, 2026
  2. alt-glitch commented on May 28, 2026

    @alt-glitch

    Duplicate of #32207 (which is itself a duplicate of #23567). Same /clear /new /reset slash command freeze on Windows — prompt_toolkit input channel deadlock. PR #33241 (merged) fixes #32383 (the Linux/macOS variant); the Windows variant was fixed by merged #32013 + #31704. If this persists on current main, it may be a new regression.

  3. daniij commented on May 28, 2026

    @daniij
    Author

    @alt-glitch Unlike previous issues that were reported using WSL, I am using the native Windows version via PowerShell.

  4. daniij commented on May 28, 2026

    @daniij
    Author

    On Hermes Agent version v0.15.0 (2026.5.28), the /new now or /reset now commands work properly, but without now, the terminal still freezes

  5. Kaabvoo commented on May 30, 2026

    @Kaabvoo

    I'm experiencing this too, I'm on:
    windows version 10.0.26200 Build 26200
    terminal version 1.24.11321.0
    hermes version v0.15.1

  6. zj-andyzhu commented on Jun 1, 2026

    @zj-andyzhu

    experiences the same thing on WSL on windows env:
    WSL 2.0
    Hermes: Hermes Agent v0.14.0 (2026.5.16)

  7. 50 remaining items

  8. added
    os/windowsNative Windows behaviour or breakage: PowerShell install, Windows paths, cmd.exe, WSL-vs-native diff
    and removed on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium — degraded but workaround existscomp/cliCLI entry point, hermes_cli/, setup wizardduplicateThis issue or pull request already existsos/windowsNative Windows behaviour or breakage: PowerShell install, Windows paths, cmd.exe, WSL-vs-native diffsweeper:implemented-on-mainSweeper: behavior already present on current mainsweeper:risk-platform-windowsSweeper risk: may break or behave differently on native Windowstype/bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions