User messages get submitted automatically mid sentence when agent messages back

[sulantha2006]

Is this a reproducible bug?

• I confirm this is a reproducible bug, not a feature request, idea, question, contribution proposal, or direction check.
• I reproduced this bug on the version and environment reported below using the exact steps provided.

Current behavior

Currently the user messages gets submitted without pressing return/enter if the agent sends a message. This happens occasioannly, not all the time when the agent responds. Issue happened with Codex, not sure if this persists with other agents. But happens often enough to be a nuisense.
Issue is present in both Linux and Mac clients with a Mac server backend.

Expected behavior

All user messages submission must be triggered by user pressing enter/return.

Reproduction

Try typing a long message while the agent is responding (doing something, and resnpodns to previous messeges), the user message gets auto submitted.

Impact

User messages gets submitted mid sentence - so only half of the message is sent to the agent and the agent acts on it. Only way to undo is to stop agent work with escape.

Environment

• Herdr version: 0.9.0
• Update channel (stable or preview): stable
• Operating system: Mac (server and client) and Ubuntu (Client)
• Terminal: Mac teminal and Ghostty both (+ Ubuntu terminal)
• Shell, if relevant: zsh (Mac) / bash(Ubuntu)
• Relevant config, if any:

[akbash-bot]

Could you capture one short input trace when this happens? It will show whether Herdr receives an Enter from the client at the unexpected submission.

1. On the Mac client, detach from Herdr with your normal prefix followed by q (default: Ctrl+B, then q). This leaves your agents running; do not stop the server.
2. In that same terminal, launch Herdr again with input logging:

   HERDR_LOG='herdr=info,herdr::raw_input=debug' herdr

   Keep any arguments from your usual launch command, such as --remote or --session, after herdr, so you reconnect to the same session.
3. Reproduce using harmless dummy text while Codex responds. As soon as the text submits without Enter, stop typing, press Escape to stop Codex, then detach again with prefix followed by q.
4. In the client terminal, run:

   grep 'herdr::raw_input' ~/.config/herdr/herdr-client.log | tail -n 200 > ~/herdr-4001-input.txt

   If you launch with --session NAME, use ~/.config/herdr/sessions/NAME/herdr-client.log instead (replace NAME with your session name).

Please paste the contents of ~/herdr-4001-input.txt and mark the last few dummy characters you typed before the unexpected submission. The trace includes typed text, paste contents, and key bytes: inspect it before sharing and do not enter passwords or private prompts during the capture. Relaunching with your usual command, without HERDR_LOG, turns this tracing off.

[sulantha2006]

I added the log you requested along with a video showing it happns. I created two agents, one I keep typing, while another sends messages to the same session. Just to conifrm, I do not press enter, touch the mouse/touch pad or to any pastes. All I do is type the letters. ( I am not sure who press the paste). I am begggining to think that this is something to do with agent communication. - though not confirmed, I was only able to reproduce when I started the 2 agent communication setup)

herdr-4004-input.txt.
Video

[hdosys]

Same, not sure there is a good solution.

[ogulcancelik]

thanks for the trace, it helped. you never pressed enter. that enter came from the other agent. when an agent sends to a pane with herdr agent prompt, it types its text and hits enter. if you're halfway through a sentence in that same pane, your draft goes out with it.

this is a known limitation (#4072 and #4712 are the same thing). there are a few ways to fix it, like holding agent messages while someone is typing in that pane, but they all need a bigger change and it's not a priority right now.

in the meantime you can tell the sending agent to check first. have it run herdr agent read <pane> before prompting, and if there's text in the input box, wait and try again. it's not perfect since you could start typing right after the check, but it should catch most of it. the other option is to keep the pane you type in separate from the ones agents send to.