feat(tui): implement PermissionsScreen as proper Textual Screen with v-key handler #10172

Open
opened 2026-04-17 04:08:31 +00:00 by HAL9000 · 0 comments
Owner

Background

The PermissionsScreen must be implemented as a proper Textual Screen (not a Static widget) to support full-screen permission management. The PermissionQuestionWidget must open this screen when the user presses v, allowing them to review and manage all pending and historical permissions without leaving the TUI.

Acceptance Criteria

  • PermissionsScreen implemented as a Textual Screen (not Static)
  • PermissionQuestionWidget opens PermissionsScreen when v key pressed
  • Permissions screen shows all pending and historical permission requests
  • Users can approve, deny, and remember decisions from the screen
  • Test coverage >= 97%

Metadata

  • Commit Message: feat(tui): implement PermissionsScreen as proper Textual Screen
  • Branch: feature/v3.7.0/tui-permissions-screen
  • Milestone: v3.7.0
  • Ref: #5310 EPIC: TUI Safety & Permission System — PermissionsScreen & Shell Safety (v3.7.0)

Subtasks

  • Implement PermissionsScreen as a Textual Screen
  • Implement PermissionQuestionWidget with v key handler
  • Implement permission list view with approve/deny/remember actions
  • Implement permission state persistence across sessions
  • Write unit tests for screen rendering and permission actions

Definition of Done

  • Implementation complete and all acceptance criteria met
  • Tests written and passing (coverage >= 97%)
  • PR reviewed and merged
  • Parent epic updated

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Background The PermissionsScreen must be implemented as a proper Textual `Screen` (not a `Static` widget) to support full-screen permission management. The `PermissionQuestionWidget` must open this screen when the user presses `v`, allowing them to review and manage all pending and historical permissions without leaving the TUI. ## Acceptance Criteria - [ ] `PermissionsScreen` implemented as a Textual `Screen` (not `Static`) - [ ] `PermissionQuestionWidget` opens `PermissionsScreen` when `v` key pressed - [ ] Permissions screen shows all pending and historical permission requests - [ ] Users can approve, deny, and remember decisions from the screen - [ ] Test coverage >= 97% ## Metadata - **Commit Message**: `feat(tui): implement PermissionsScreen as proper Textual Screen` - **Branch**: `feature/v3.7.0/tui-permissions-screen` - **Milestone**: v3.7.0 - **Ref**: #5310 EPIC: TUI Safety & Permission System — PermissionsScreen & Shell Safety (v3.7.0) ## Subtasks - [ ] Implement `PermissionsScreen` as a Textual `Screen` - [ ] Implement `PermissionQuestionWidget` with `v` key handler - [ ] Implement permission list view with approve/deny/remember actions - [ ] Implement permission state persistence across sessions - [ ] Write unit tests for screen rendering and permission actions ## Definition of Done - Implementation complete and all acceptance criteria met - Tests written and passing (coverage >= 97%) - PR reviewed and merged - Parent epic updated --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#10172
No description provided.