TUI rendering & message duplication issues: input box hard to focus, repeated system messages, rapid log spam, unstable file writing, occasional crashesUI rendering & message duplication issues: input box hard to focus, repeated system messages, rapid log spam, unstable file writing, occasional crashes

[TomikawaHashina]

Summary
I’m experiencing multiple usability-impacting UI/interaction issues in Continue: input box rendering glitches/hard-to-focus, repeated system messages while typing, repeated “previous stage conclusion” spam while waiting for interaction, extreme log spam during file-writing that obscures my own input, unstable file creation (no actual file produced), and occasional unexpected crashes.

---

Issues

1. Input box rendering & focus issues
   -On the first input, the upper area of the input box keeps adding “lines” (visual artifacts). Also, the input field is hard to focus/select reliably (clicking often fails to place the cursor).

2. System message duplicates while typing
   -While typing, each character triggers the previous system message to re-appear/duplicate (as if the last system message is being re-inserted or re-rendered repeatedly).

3. Repeated “previous stage conclusion” while waiting
   -When it’s waiting for my next interaction (before I type/click anything), it repeatedly spams the previous stage’s execution conclusion, as if stuck in a loop.

4. Severe log spam during file-writing
   -When I instruct it to write files locally, there’s a countdown at the bottom, but the top keeps rapidly refreshing “what it’s doing” (~4–5 lines per second). This log spam obscures or mixes with my input so I can’t see what I’m typing—only the final result is readable. Overall UX is very poor.

5.Unstable file creation
-I explicitly ask it to write files locally. Sometimes it responds as if it completed the task, but no file is actually created on disk. I have to retry or re-run the conversation to get the file produced.

6. Occasional crash while coding
   -It occasionally crashes during coding sessions—especially when the UI is spamming logs. It exits without warning, which severely impacts the experience.

---

Steps to reproduce

1. Open Continue and start a new chat/session.
2. Click the input box and type for the first time; observe whether the upper area shows accumulating line artifacts and whether focus is hard to obtain.
3. Continue typing; observe whether the previous system message duplicates on every character.
4. Stop typing and wait; observe whether it repeatedly spams the previous stage conclusion.
5. Send a “write file locally” instruction (e.g., create/write file xxx); during the countdown, observe high-frequency log spam and whether it obscures input.
6. Verify whether the file is actually created; repeat multiple times to see intermittent failures.
7. During log spam, keep coding/interacting and check for sudden crashes.

---

Expected
Stable focusable input with no rendering artifacts; typing should not duplicate system messages; no repeated conclusions while waiting; file-writing logs should be throttled/collapsible and never obscure input; file creation should be reliable with clear error reporting on failure; no unexpected crashes.