story-kit: create 168_bug_agent_message_queue_limited_to_one_line
This commit is contained in:
@@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
type: bug
|
||||||
|
title: Agent message queue limited to one line
|
||||||
|
---
|
||||||
|
|
||||||
|
# Bug 168: Agent message queue limited to one line
|
||||||
|
|
||||||
|
## Description
|
||||||
|
|
||||||
|
Story 155 added the ability to queue messages while an agent is busy. However, the queue appears to be limited to a single line — if you type multiple messages while the agent is working, only the last one is retained. Users need to be able to queue multiple messages.
|
||||||
|
|
||||||
|
## How to Reproduce
|
||||||
|
|
||||||
|
1. Open the web UI and start a conversation with a busy agent
|
||||||
|
2. Type and send a message while the agent is processing
|
||||||
|
3. Type and send a second message
|
||||||
|
4. Observe that only the most recent queued message is shown/retained
|
||||||
|
|
||||||
|
## Expected Result
|
||||||
|
|
||||||
|
Multiple queued messages should be retained and delivered to the agent in order when it becomes available.
|
||||||
|
|
||||||
|
## Key files
|
||||||
|
|
||||||
|
- `frontend/src/components/` — chat/agent interaction components where message queuing is implemented
|
||||||
|
- `server/src/` — if server-side queuing is involved
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] Users can queue multiple messages while an agent is busy
|
||||||
|
- [ ] Queued messages are delivered in order
|
||||||
|
- [ ] UI shows all queued messages, not just the latest
|
||||||
|
- [ ] All tests pass
|
||||||
Reference in New Issue
Block a user