hermes - 💡(How to fix) Fix TUI: Add inline ghost-text auto-suggest (parity with CLI) [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
NousResearch/hermes-agent#15495Fetched 2026-04-26 05:27:04
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Root Cause

The inline suggest is the single biggest "feel" difference between CLI and TUI. Without it, the TUI input feels inert — you have to explicitly invoke Tab to discover completions. With ghost-text, the input feels alive and the user discovers commands passively while typing. This is the #1 reason users perceive the TUI as "limited" compared to CLI.

RAW_BUFFERClick to expand / collapse

Problem

The CLI (prompt_toolkit) has inline ghost-text auto-suggest that makes input feel responsive and "ahead of you" — as you type /upd, dim text ate appears inline. The TUI (Ink/React) lacks this entirely, which makes the TUI feel noticeably more limited despite having equivalent tab-completion.

Current state

CLI has:

  • SlashCommandAutoSuggest — inline ghost-text for slash commands and subcommands (e.g., /mod → dim el)
  • Falls back to history-based inline suggestions for regular text
  • Tab completion dropdown (slash commands, paths, @ context references)

TUI has:

  • Tab completion dropdown via useCompletion.ts → RPC complete.slash / complete.path (reuses the same SlashCommandCompleter backend)
  • No inline ghost-text auto-suggest — this is the gap

Proposed solution

Add an inline auto-suggest layer to the TUI composer that:

  1. Shows ghost-text (dim, appended after cursor) for slash commands as the user types — matching the CLI SlashCommandAutoSuggest behavior
  2. Falls back to history-based suggestions for non-slash input
  3. Accepts suggestion with Right arrow / End / Tab (standard conventions)

Implementation options:

  • New RPC method (e.g., complete.suggest) that returns a single inline suggestion given current input, reusing SlashCommandAutoSuggest on the backend
  • Or port the suggestion logic to TypeScript client-side

Why this matters

The inline suggest is the single biggest "feel" difference between CLI and TUI. Without it, the TUI input feels inert — you have to explicitly invoke Tab to discover completions. With ghost-text, the input feels alive and the user discovers commands passively while typing. This is the #1 reason users perceive the TUI as "limited" compared to CLI.

extent analysis

TL;DR

Implement an inline auto-suggest layer in the TUI composer to provide ghost-text suggestions for slash commands and non-slash input.

Guidance

  • To achieve the desired functionality, consider adding a new RPC method (e.g., complete.suggest) that returns a single inline suggestion given the current input, reusing the SlashCommandAutoSuggest logic on the backend.
  • Alternatively, port the suggestion logic to TypeScript client-side to enable inline suggestions without additional backend changes.
  • Ensure the inline auto-suggest layer accepts suggestions with standard conventions such as Right arrow, End, or Tab.
  • Implement a fallback to history-based suggestions for non-slash input to maintain a consistent user experience.

Example

No code example is provided as the issue does not contain specific implementation details.

Notes

The proposed solution aims to bridge the gap between the CLI and TUI by introducing inline ghost-text auto-suggest in the TUI composer. However, the implementation details and potential challenges are not discussed in the issue.

Recommendation

Apply a workaround by implementing the proposed solution, either by adding a new RPC method or porting the suggestion logic to the client-side, to provide an inline auto-suggest layer in the TUI composer. This will help to improve the user experience and reduce the perceived limitations of the TUI compared to the CLI.

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