[Feature Request] Interactive step confirmation with arrow-key selection in chat UI

Resolved 💬 3 comments Opened Jan 23, 2026 by armatrix Closed Jan 27, 2026

Bug Description
Title: Feature Request: Interactive Step Confirmation in Chat (Arrow Key Selection + Optional Input)

Context / Use Case
When using Claude Code skills like /goframe for multi-step workflows, I need explicit review checkpoints before
key actions (e.g., make dao, make ctrl, make service, SQL changes, file generation). Currently this requires
replying with plain text, which is error‑prone and easy to miss in complex flows.

Requested Capability
Provide interactive confirmation prompts inside the chat UI that support:

  • Arrow‑key selection (Proceed / Skip / Stop)
  • Enter to confirm
  • Optional text input for notes (e.g., reason for Skip)

Ideal Interaction Example
Prompt:
“About to run make ctrl. Please choose:”
[↑↓ select] Proceed / Skip / Stop
Optional input: ________

Value

  • Reduces accidental actions
  • Improves control for multi‑step engineering workflows
  • Aligns with team/framework constraints
  • Better auditability for critical steps

Current Workaround
I can run terminal scripts (gum/fzf), but the interaction is outside the chat and feels disconnected.

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 2.1.17
  • Feedback ID: a7e84462-844d-449b-9eb4-da18530922b6

Errors

[{"error":"Error: ENOENT: no such file or directory, scandir '/Library/Application Support/ClaudeCode/.claude/skills'\n    at readdirSync (unknown)\n    at <anonymous> (/$bunfs/root/claude:12:1903)\n    at vW (/$bunfs/root/claude:11:35097)\n    at readdirSync (/$bunfs/root/claude:12:1864)\n    at y2R (/$bunfs/root/claude:1479:380)\n    at y2R (/$bunfs/root/claude:1479:1350)\n    at <anonymous> (/$bunfs/root/claude:1479:4440)\n    at <anonymous> (/$bunfs/root/claude:1479:5171)\n    at A (/$bunfs/root/claude:11:7244)\n    at pX8 (/$bunfs/root/claude:4784:4342)","timestamp":"2026-01-23T11:32:55.460Z"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗