Summary
Developers have requested a CLI-first or hybrid CLI/GUI workflow option. The current GUI-first model is seen as friction by some users who prefer managing setup, repository selection, plan management, execution, and status from the terminal.
Requirements
- Define a supported CLI surface for main workflows while maintaining compatibility with the GUI
- Users should be able to complete core actions without opening the GUI
- CLI output must include clear status and failure details
- GUI and CLI workflows must stay in sync on the same project state
Context
This finding comes from Tendril Test Submission feedback.
Reported by Christopher Clemons
https://ivy-interactive.slack.com/archives/C0AS51ABBB6/p1780061145437109?thread_ts=1780061145.437109&cid=C0AS51ABBB6
Summary
Developers have requested a CLI-first or hybrid CLI/GUI workflow option. The current GUI-first model is seen as friction by some users who prefer managing setup, repository selection, plan management, execution, and status from the terminal.
Requirements
Context
This finding comes from Tendril Test Submission feedback.
Reported by Christopher Clemons
https://ivy-interactive.slack.com/archives/C0AS51ABBB6/p1780061145437109?thread_ts=1780061145.437109&cid=C0AS51ABBB6