Problem
During tasks that take more than a few seconds (e.g., Compose), the user has limited visibility into what's happening. The MCP client would need to constantly pause and send status updates to provide progress info, which slows down the actual work.
Proposed solution
Research whether there's a way to get more detailed, real-time status information from the MCP client during long-running tasks without requiring the client to explicitly stop and send a status update. For example, streaming partial progress or piggy-backing status on existing sync traffic.
This is a research/exploration issue — the outcome may be "not feasible" and that's a valid result.
Problem
During tasks that take more than a few seconds (e.g., Compose), the user has limited visibility into what's happening. The MCP client would need to constantly pause and send status updates to provide progress info, which slows down the actual work.
Proposed solution
Research whether there's a way to get more detailed, real-time status information from the MCP client during long-running tasks without requiring the client to explicitly stop and send a status update. For example, streaming partial progress or piggy-backing status on existing sync traffic.
This is a research/exploration issue — the outcome may be "not feasible" and that's a valid result.