gemini-cli - 💡(How to fix) Fix [Voice] Cursor-Aware Insertion [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25494Fetched 2026-04-16 07:05:35
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×3cross-referenced ×1

Currently, new voice transcriptions are appended to the very end of the input buffer. To make it easier to edit and build long prompts, the transcribed text should be inserted exactly where the user's cursor is currently located.

Root Cause

Currently, new voice transcriptions are appended to the very end of the input buffer. To make it easier to edit and build long prompts, the transcribed text should be inserted exactly where the user's cursor is currently located.

RAW_BUFFERClick to expand / collapse

Description

Currently, new voice transcriptions are appended to the very end of the input buffer. To make it easier to edit and build long prompts, the transcribed text should be inserted exactly where the user's cursor is currently located.

Requirements

  • Update the InputPrompt or related components to splice the transcribed text at the cursor index instead of appending.

Epic: #24175

extent analysis

TL;DR

Update the InputPrompt component to insert transcribed text at the cursor index instead of appending it to the end of the input buffer.

Guidance

  • Review the current implementation of the InputPrompt component to understand how it handles text insertion and cursor positioning.
  • Identify the specific function or method responsible for appending new transcriptions to the input buffer and modify it to insert text at the cursor index instead.
  • Consider using a library or framework function that provides a way to insert text at a specific position in a string or text buffer, if available.
  • Test the updated component with various cursor positions and transcription lengths to ensure correct functionality.

Example

// Pseudocode example, actual implementation may vary
const insertTranscription = (transcription, cursorIndex, inputBuffer) => {
  const textBeforeCursor = inputBuffer.slice(0, cursorIndex);
  const textAfterCursor = inputBuffer.slice(cursorIndex);
  return textBeforeCursor + transcription + textAfterCursor;
};

Notes

The exact implementation details may depend on the specific requirements and constraints of the project, such as the technology stack and framework used.

Recommendation

Apply workaround: Update the InputPrompt component to insert transcribed text at the cursor index, as this is a specific and targeted change that addresses the described issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING