This commit is contained in:
12
.ideai/tickets/167/carnet.md
Normal file
12
.ideai/tickets/167/carnet.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
issueRef: "#167"
|
||||
version: 2
|
||||
updatedBy: {"kind":"agent","agent_id":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d"}
|
||||
updatedAt: 1786034876685
|
||||
---
|
||||
## 2026-08-06 — New regression ticket from user test
|
||||
- User validated that classic progress messages stream correctly in the custom CLI.
|
||||
- However, provider turn-end events and MCP/tool-call events are rendered only after the final answer is already displayed.
|
||||
- This is misleading because locally observable IdeA events should appear in temporal order before `Final`, not be appended retroactively afterward.
|
||||
- Scope for this cycle: determine whether the bug sits in event buffering/order at the backend stream model, transport to frontend, or frontend reconciliation/render ordering; fix and validate on the real AppImage.
|
||||
- Main created the ticket and will run the full cycle with Architect, Git, implementation, QA, and final AppImage rebuild.
|
||||
17
.ideai/tickets/167/issue.md
Normal file
17
.ideai/tickets/167/issue.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
id: "90559b5d-eb4d-47e5-b18f-cb2dc0ab5080"
|
||||
number: 167
|
||||
title: "Custom CLI: turn-end and MCP/tool events appear only after Final"
|
||||
status: "open"
|
||||
priority: "high"
|
||||
sprint: null
|
||||
links: []
|
||||
agentRefs: [{"agentId":"fe887179-933f-47d4-960f-c3b06827f86c","role":"assigned"},{"agentId":"8f7da528-58df-4315-97e9-0562230ecc19","role":"assigned"}]
|
||||
attachments: []
|
||||
createdBy: {"kind":"agent","agent_id":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d"}
|
||||
updatedBy: {"kind":"agent","agent_id":"a6c6ea12-bfc6-4bdc-8031-324102dfa34d"}
|
||||
createdAt: 1786034864702
|
||||
updatedAt: 1786034876685
|
||||
version: 2
|
||||
---
|
||||
Régression observée sur la custom CLI (test utilisateur du 2026-08-06): les messages de progress classiques apparaissent bien pendant le tour, mais les événements de fin de tour (`turn.started`/`turn.completed` côté provider) et les appels MCP/outils n'apparaissent qu'après le rendu du Final. Attendu: tout événement IdeA observable localement avant Final doit être projeté au fil de l'eau dans le bon ordre temporel, sans post-affichage trompeur après la réponse finale.
|
||||
Reference in New Issue
Block a user