[FEATURE] UX for /workflow is missing some info / actual state of running task(s)
Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 20, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When a workflow or agent runs in the background, the assistant cannot relay the intermediate status to the user : one has to check /workflows manually. The request is for a progress API accessible to the assistant during execution, not just at the end...
PLEASE FIX THIS :)
Proposed Solution
Proposed Solution / Ideal UX
When a workflow or background agent is running, the assistant should be able to query its live status on demand ( not just receive a final notification. Concretely:
- When the user asks "is it done?" or "any progress?", the assistant should be able to call something like TaskStatus(id) or read a live progress stream, and reply with the current phase, % complete, and active sub-agents.
- Alternatively, the assistant should proactively push a short status update every N minutes while a long task runs, without the user having to ask.
- The /workflows progress tree is good , but it's only visible to the user, not to the assistant. Bridging that gap (exposing the same data to the assistant at query time) would solve the problem.
Right now the assistant is blind between "launched" and "completed", which forces the user to monitor progress themselves , defeating the purpose of delegating to a background agent.
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_