Nice to have: Interactive Runtime CLI #1092

New issue

Open

opened 2025-10-14 16:50:01 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:50:01 -06:00

Owner

Originally created by @eyaltoledano on 3/29/2025

“I find it hard to see in Cursor what task-master is doing. I kind of want a UI that I can have open and see what is going on. This could be a web UI or a view in the console tool. It would be nice to see the tasks that are written and what tasks are upcoming to know if I should be re-arranging the tasks or not.”

Motivation

Currently, TaskMaster CLI runs commands individually and exits after each execution. This workflow can feel static, interrupts continuity, and restricts opportunities for a richer, more interactive user experience.

Creating an interactive runtime environment for TaskMaster would make the CLI feel alive, responsive, and dynamic. Users could perform multiple actions without restarting the CLI, enabling real-time feedback, dynamic UI elements, and improved user engagement.

Proposed Solution

Transform TaskMaster CLI into an interactive runtime, similar to REPL (Read-Eval-Print Loop), providing continuous sessions rather than single-command executions.

In this new mode:

Commands execute within a persistent interactive environment.
Real-time data (e.g., token usage, task statuses, or other dynamic info) can update and display interactively.
UI elements become clickable/selectable, improving interactivity beyond what's achievable with traditional command-line parsing libraries (like Commander).

Key Elements

Persistent CLI Session:
- Users start TaskMaster once (task-master start) and perform multiple commands within the same session.
Interactive Elements:
- Implement clickable buttons, navigable menus, and real-time-updating status indicators within the terminal (powered by libraries like Ink or similar interactive CLI frameworks).
Real-time Updates:
- Information such as token usage, task progress, or status messages update dynamically during the session without needing to exit and re-enter commands.
Enhanced User Experience:
- Command suggestions/autocomplete.
- Easy navigation through command history and task lists.

Example Workflow

User initiates a runtime session:

$ task-master start
→ TaskMaster interactive session started!

Inside the interactive session (illustrative example):

TaskMaster > [Create Task]  [View Tasks]  [Sync README]  

Token Usage: 324 tokens used today (updates live)

> [Create Task] clicked
  → "Describe your new task:" __

After completing actions, user exits:

TaskMaster > exit
✓ Interactive session ended.

Implementation Considerations

Transition from Commander.js to interactive CLI libraries (e.g., Ink, Enquirer) to facilitate UI/UX enhancements.
Ensure backward compatibility, keeping standard one-off commands still available.
Plan for additional complexity (e.g., state management and session handling).
Has to play nice with #11

Out of Scope (Future Considerations)

Web-based GUI or native desktop apps.
Fully graphical interface beyond CLI capabilities.

*Originally created by @eyaltoledano on 3/29/2025* > “I find it hard to see in Cursor what task-master is doing. I kind of want a UI that I can have open and see what is going on. This could be a web UI or a view in the console tool. It would be nice to see the tasks that are written and what tasks are upcoming to know if I should be re-arranging the tasks or not.” ## Motivation Currently, TaskMaster CLI runs commands individually and exits after each execution. This workflow can feel static, interrupts continuity, and restricts opportunities for a richer, more interactive user experience. Creating an interactive runtime environment for TaskMaster would make the CLI feel alive, responsive, and dynamic. Users could perform multiple actions without restarting the CLI, enabling real-time feedback, dynamic UI elements, and improved user engagement. ## Proposed Solution Transform TaskMaster CLI into an interactive runtime, similar to REPL (Read-Eval-Print Loop), providing continuous sessions rather than single-command executions. In this new mode: - Commands execute within a persistent interactive environment. - Real-time data (e.g., token usage, task statuses, or other dynamic info) can update and display interactively. - UI elements become clickable/selectable, improving interactivity beyond what's achievable with traditional command-line parsing libraries (like Commander). ## Key Elements - **Persistent CLI Session**: - Users start TaskMaster once (`task-master start`) and perform multiple commands within the same session. - **Interactive Elements**: - Implement clickable buttons, navigable menus, and real-time-updating status indicators within the terminal (powered by libraries like Ink or similar interactive CLI frameworks). - **Real-time Updates**: - Information such as token usage, task progress, or status messages update dynamically during the session without needing to exit and re-enter commands. - **Enhanced User Experience**: - Command suggestions/autocomplete. - Easy navigation through command history and task lists. ## Example Workflow User initiates a runtime session: ``` $ task-master start → TaskMaster interactive session started! ``` Inside the interactive session (illustrative example): ``` TaskMaster > [Create Task] [View Tasks] [Sync README] Token Usage: 324 tokens used today (updates live) > [Create Task] clicked → "Describe your new task:" __ ``` After completing actions, user exits: ``` TaskMaster > exit ✓ Interactive session ended. ``` **Implementation Considerations** - Transition from Commander.js to interactive CLI libraries (e.g., Ink, Enquirer) to facilitate UI/UX enhancements. - Ensure backward compatibility, keeping standard one-off commands still available. - Plan for additional complexity (e.g., state management and session handling). - Has to play nice with #11 **Out of Scope (Future Considerations)** - Web-based GUI or native desktop apps. - Fully graphical interface beyond CLI capabilities.