Terminal Cursor appears on wrong line when prompt is more than 1 line long

[ordo-n]

Issue summary

I have been noticing when the prompt is more than 1 line long the terminal cursor appears on wrong line

I notice this at mobile resolutions

Expected behavior

Cursor is supposed to appear at the end of line 2

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Meta Quest 3S - Keyboard not functioning as expected #1023

Related Issues

• term.resume and prompt issues #1022
• Uncaught TypeError: can't access property "substring", u[n] is undefined OR Cannot read properties of undefined (reading 'substring') #1026
• Timeout with no delay causing the page to freeze #1032

👤 Suggested Assignees

• ordo-n
• ok-coder1
• leeharr

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[jcubic]

Is it raw prompt? If you use raw prompt you ignore everything what the library is doing, like line wrapping and handling of multiline prompt. I'm not sure if you can do anything if you render prompt yourself with HTML.

[ordo-n]

I have been noticing this since before the raw prompt was added.

[jcubic]

Can you create a reproduction. This only happens when you have raw prompt.

The line wrapping in prompt is battle tested. The library creates a span for each line. And the cursor always appear after last span.

If you want the same behavior with raw prompt you need split the prompt yourself and you need to do this in resize for the output to be responsive.

[ordo-n]

I’ve been trying to create a minimal reproduction for the raw prompt case, but so far I haven’t been able to trigger it reliably. I’m going back through my styling and layout (especially anything affecting width, white-space, and resize handling) to make sure I’m not accidentally masking or causing it.

While digging through this, I also came across another potential issue (see attached screenshot).

This one seems unrelated to prompt wrapping and occurs during touch handling — specifically around focus/blur logic inside the touchend.terminal path. I haven’t fully isolated it yet, but wanted to flag it in case it’s something you recognise or want me to narrow down further.

I’ll continue trying to produce a minimal repro for both cases and report back once I have something concrete.