UAT: TUI Sessions Screen entirely absent — spec requires dedicated screen for session management (create, resume, delete, export) #2952

Open
opened 2026-04-05 02:55:13 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: feat/tui-sessions-screen
  • Commit Message: feat(tui): implement Sessions Screen for session management
  • Milestone: v3.7.0
  • Parent Epic: #868

Background and Context

The spec defines a Sessions Screen as a dedicated TUI screen that provides an overview of all active and past sessions. This screen is a core part of the TUI experience, allowing users to manage their conversation sessions with orchestrators. Discovered during UAT testing: the src/cleveragents/tui/screens/ directory exists but is completely empty (contains only __pycache__), meaning the entire Sessions Screen feature is absent from the implementation.

This issue also affects PR #1302 (feat(tui): implement Textual MainScreen), which is open but does not include a Sessions Screen.

Current Behavior

The src/cleveragents/tui/screens/ directory exists but is completely empty (contains only __pycache__). No SessionsScreen implementation exists anywhere in the TUI codebase. The only session-related functionality is the /session slash command in commands.py, which provides basic session show/export/import but no dedicated screen UI.

Steps to reproduce:

  1. Launch the TUI: agents tui
  2. Attempt to navigate to a Sessions Screen (no such screen exists)
  3. The TUI only shows a single main screen with no session management UI

Expected Behavior

Per the specification, a dedicated SessionsScreen Textual screen class should exist in src/cleveragents/tui/screens/ that displays all active and past sessions with options to:

  • Create New Sessions: Start a new conversation with an orchestrator
  • Resume Existing Sessions: Re-open a previous session to continue the conversation
  • Delete Sessions: Permanently delete a session and its history
  • Export Sessions: Export a session's conversation history to a file

Code location: src/cleveragents/tui/screens/ (directory is empty)

Subtasks

  • Create src/cleveragents/tui/screens/sessions_screen.py with SessionsScreen class
  • Implement session list display (active and past sessions)
  • Implement create new session action
  • Implement resume existing session action
  • Implement delete session action with confirmation dialog
  • Implement export session action
  • Add navigation binding to reach Sessions Screen from main screen
  • Write BDD scenarios in features/tui_sessions_screen.feature

Definition of Done

  • SessionsScreen class exists and is navigable from the main TUI
  • All four session management actions (create, resume, delete, export) are functional
  • Confirmation dialog shown for destructive delete action
  • BDD scenarios cover all screen functionality
  • nox -e typecheck passes
  • nox -e unit_tests passes
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-new-issue-creator

## Metadata - **Branch**: `feat/tui-sessions-screen` - **Commit Message**: `feat(tui): implement Sessions Screen for session management` - **Milestone**: v3.7.0 - **Parent Epic**: #868 ## Background and Context The spec defines a Sessions Screen as a dedicated TUI screen that provides an overview of all active and past sessions. This screen is a core part of the TUI experience, allowing users to manage their conversation sessions with orchestrators. Discovered during UAT testing: the `src/cleveragents/tui/screens/` directory exists but is completely empty (contains only `__pycache__`), meaning the entire Sessions Screen feature is absent from the implementation. This issue also affects PR #1302 (`feat(tui): implement Textual MainScreen`), which is open but does not include a Sessions Screen. ## Current Behavior The `src/cleveragents/tui/screens/` directory exists but is completely empty (contains only `__pycache__`). No `SessionsScreen` implementation exists anywhere in the TUI codebase. The only session-related functionality is the `/session` slash command in `commands.py`, which provides basic session show/export/import but no dedicated screen UI. Steps to reproduce: 1. Launch the TUI: `agents tui` 2. Attempt to navigate to a Sessions Screen (no such screen exists) 3. The TUI only shows a single main screen with no session management UI ## Expected Behavior Per the specification, a dedicated `SessionsScreen` Textual screen class should exist in `src/cleveragents/tui/screens/` that displays all active and past sessions with options to: - **Create New Sessions**: Start a new conversation with an orchestrator - **Resume Existing Sessions**: Re-open a previous session to continue the conversation - **Delete Sessions**: Permanently delete a session and its history - **Export Sessions**: Export a session's conversation history to a file Code location: `src/cleveragents/tui/screens/` (directory is empty) ## Subtasks - [ ] Create `src/cleveragents/tui/screens/sessions_screen.py` with `SessionsScreen` class - [ ] Implement session list display (active and past sessions) - [ ] Implement create new session action - [ ] Implement resume existing session action - [ ] Implement delete session action with confirmation dialog - [ ] Implement export session action - [ ] Add navigation binding to reach Sessions Screen from main screen - [ ] Write BDD scenarios in `features/tui_sessions_screen.feature` ## Definition of Done - [ ] `SessionsScreen` class exists and is navigable from the main TUI - [ ] All four session management actions (create, resume, delete, export) are functional - [ ] Confirmation dialog shown for destructive delete action - [ ] BDD scenarios cover all screen functionality - [ ] `nox -e typecheck` passes - [ ] `nox -e unit_tests` passes - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator
freemo added this to the v3.7.0 milestone 2026-04-05 02:55:17 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Confirmed
  • MoSCoW: Should Have

Valid finding verified during batch triage.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Confirmed - **MoSCoW**: Should Have Valid finding verified during batch triage. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
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.

Blocks
Reference
cleveragents/cleveragents-core#2952
No description provided.