You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v2: add optimistic UI while MCP prompt commands resolve #34860
V2 slash commands backed by MCP prompts can take noticeable time to resolve because command submission must call the MCP server's prompt resolution path before the prompt is admitted to the session.
Today there is no optimistic/pending UI for that resolution phase. If an MCP prompt command is slow, the submit experience can look like the prompt input is stalled or in an odd intermediate state before the resolved prompt appears in the session.
Expected behavior
After submitting an MCP prompt slash command, the TUI should immediately show an explicit pending/submitted command state while the server resolves the MCP prompt. The user should not be left looking at an apparently idle or stuck prompt input during that wait.
Reproduction aid
Temporarily add an artificial delay before MCP prompt evaluation:
Then submit an MCP prompt slash command with arguments. The UI should make the command resolution phase obvious and non-confusing during the artificial delay.
I’d like to take this on. I’ve traced the current TUI submission path and plan to add a small pending/resolving state that appears immediately after an MCP-backed slash command is submitted, clears when resolution completes or fails, and is covered by a delayed-resolution regression test. Does that interaction and scope match what you had in mind?
Activity
zanemo109 commentedon Aug 2, 2026
I’d like to take this on. I’ve traced the current TUI submission path and plan to add a small pending/resolving state that appears immediately after an MCP-backed slash command is submitted, clears when resolution completes or fails, and is covered by a delayed-resolution regression test. Does that interaction and scope match what you had in mind?