Expose the agent's permission/plan mode as a control in the prompt box #256

Activity

1. LarryHu0217 commented on Aug 9, 2026

   

   LarryHu0217

   on Aug 9, 2026

   Contributor

   More actions

   I checked this against current main (d000fff). Sending Claude's mode-cycle key from PromptInput is straightforward (\x1b[Z), but the app currently has no authoritative permission-mode state. The only observable source is Claude's rendered PTY footer, and getAgentOutputTail() is not itself reactive. Tracking the mode only after button clicks would drift whenever the user presses Shift+Tab in the terminal.

   Would you be comfortable with a Claude-only first pass that:

   • parses normalized PTY frames into default, accept edits, plan, or bypass permissions when Claude exposes one of those footer labels;
   • shows the control only for Claude Code, with an explicit unknown state until a recognizable footer is observed;
   • sends exactly one Shift+Tab sequence per click while keeping focus in the prompt box; and
   • uses recorded-frame tests for mode detection plus a focused control test for the PTY write?

   I would avoid optimistically cycling local state, so the displayed value always comes back from the agent's output. If that scope matches what you want, I can take it.