Maya Murad

Status quo: CUA models returns coordinates to describe where click events are happening on screen Desired behavior: replace coordinates by GUI location easy to understand for end users (e.g. sidebar,...

**Goal**: understand FE design, emphasizing extensibility (scoped to skeleton). We can iterate on this document going forward To do: - Include component diagram

Status quo: task execution requires 2 docker containers (one for CUA, code)

User stories: * As a user, I can schedule tasks via NL * As a user, I can easily find and update previously scheduled tasks * (Notification TBD)

User stories * I can easily undo agent actions (undo is limited to renaming / moving folders). TBD for Deleterions ( _Deletions there should be a big red flag that...

User stories: * During onboarding, I can easily specify which files/folders MAGUI has access to on my local file system

User stories: * As a user, I want to monitor concurrently running tasks in one view * As a user, I want to easily access all my tasks so that...

Tasks: - [ ] Understand limitations of initial PoC #409 at prioritized scheduled + monitoring tasks - [ ] Discuss with research team how to improve existing architecture to better...

**User story:** As a user, I want my in-progress tasks to resume when I reconnect/launch the MAGUI app. Current behavior: all in progress tasks are stopped when websocket disconnects