feat(tui): implement shell safety blocking behavior and safety profile display #10173

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

Background

Shell safety blocking prevents dangerous shell commands from executing without explicit user confirmation. The TUI must support both blocking mode (requires confirmation for all shell commands) and non-blocking mode (allows shell commands without confirmation). The active safety profile must be visible in the TUI to inform users of current restrictions.

Acceptance Criteria

  • Shell safety blocking mode implemented (requires confirmation for ! commands)
  • Non-blocking mode allows ! commands without confirmation
  • Safety mode configurable via safety:set slash command
  • Active safety profile name displayed in TUI status bar
  • Dangerous command patterns (rm -rf, etc.) always require confirmation regardless of mode
  • Test coverage >= 97%

Metadata

  • Commit Message: feat(tui): implement shell safety blocking and safety profile display
  • Branch: feature/v3.7.0/tui-shell-safety-blocking
  • Milestone: v3.7.0
  • Ref: #5310 EPIC: TUI Safety & Permission System — PermissionsScreen & Shell Safety (v3.7.0)

Subtasks

  • Implement shell safety blocking mode with confirmation dialog
  • Implement non-blocking mode bypass
  • Implement dangerous command pattern detection
  • Implement safety:set slash command for mode switching
  • Implement safety profile display in TUI status bar
  • Write unit tests for safety blocking and pattern detection

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 Shell safety blocking prevents dangerous shell commands from executing without explicit user confirmation. The TUI must support both blocking mode (requires confirmation for all shell commands) and non-blocking mode (allows shell commands without confirmation). The active safety profile must be visible in the TUI to inform users of current restrictions. ## Acceptance Criteria - [ ] Shell safety blocking mode implemented (requires confirmation for `!` commands) - [ ] Non-blocking mode allows `!` commands without confirmation - [ ] Safety mode configurable via `safety:set` slash command - [ ] Active safety profile name displayed in TUI status bar - [ ] Dangerous command patterns (rm -rf, etc.) always require confirmation regardless of mode - [ ] Test coverage >= 97% ## Metadata - **Commit Message**: `feat(tui): implement shell safety blocking and safety profile display` - **Branch**: `feature/v3.7.0/tui-shell-safety-blocking` - **Milestone**: v3.7.0 - **Ref**: #5310 EPIC: TUI Safety & Permission System — PermissionsScreen & Shell Safety (v3.7.0) ## Subtasks - [ ] Implement shell safety blocking mode with confirmation dialog - [ ] Implement non-blocking mode bypass - [ ] Implement dangerous command pattern detection - [ ] Implement `safety:set` slash command for mode switching - [ ] Implement safety profile display in TUI status bar - [ ] Write unit tests for safety blocking and pattern detection ## 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#10173
No description provided.