[Bug] Mention chip obscures the caret and disrupts CJK IME editing #307

Affected area

Desktop app

Installation method

Built from source

Lody version or commit

94bede9

Operating system

macOS arm64

Agent or runtime

Any composer session using @ session mentions

What happened?

After inserting a session mention into the Chat composer, moving the caret to the text immediately before or after the mention can produce editing glitches. When the caret lands inside an opaque mention chip, the native caret is hidden. If the mention is at the beginning of the draft, moving left can make the caret appear to disappear entirely. During Chinese/Japanese/Korean IME composition near a mention, the transient preedit text can become visually misaligned or duplicate/shift around the chip.

What did you expect?

Mention chips should remain visually styled without covering the native caret. The caret should stay visible at both mention boundaries, and IME preedit text should remain aligned while the committed mention range stays intact.

How can we reproduce it?

1. Open a Chat composer with session mentions enabled.
2. Type ordinary text, insert a session with @, and leave text on either side of the chip.
3. Move the caret with the arrow keys or pointer to just before and just after the mention; also try a mention at offset 0 and move left.
4. Repeat with a Chinese IME active and type a short preedit string adjacent to the mention.
5. Observe the hidden/displaced caret or the misaligned composition text.

How often does it happen?

Every time

Relevant log output

Additional context

The issue is isolated to the live composer overlay made of a native textarea plus mention mirrors. It does not change the text sent to the agent; it affects caret visibility, atomic mention editing, and IME rendering.

Before submitting

• I searched the existing issues and did not find a duplicate.
• This report concerns an open-source component in this repository, not a hosted service, Web or mobile app, account, or billing issue.
• This is not a security vulnerability; security reports follow the repository's security policy.
• I removed credentials, private source, conversations, prompts, personal data, and other sensitive information.