Investigate: compare task web vs Studio tasks, plan improvements

t-460·WorkTask·
·
·
Created1 month ago·Updated1 month ago

Description

Edit

Investigate and improve Studio's task section by comparing with task web.

Problem

The task section in Studio (agentd studio) is much less developed than the standalone task web UI. Need to identify gaps and plan improvements.

Investigation Approach

Use an agent with DevBrowser to:

1. Start both servers `bash # Terminal 1: task web tmux new-window -n taskweb -d "task web --port 8090"

# Terminal 2: studio tmux new-window -n studio -d "agentd studio --port 8091" `

2. Screenshot and compare with DevBrowser

  • Navigate to both UIs
  • Screenshot each page/view
  • Document features available in each

3. Feature comparison checklist

| Feature | task web | Studio | |---------|----------|--------| | Task list view | ? | ? | | Task detail view | ? | ? | | Create task | ? | ? | | Edit task | ? | ? | | Task comments | ? | ? | | Epic/subtask tree | ? | ? | | Status filtering | ? | ? | | Priority display | ? | ? | | Search | ? | ? | | Markdown rendering | ? | ? | | Mobile responsive | ? | ? |

4. Produce improvement plan

  • List missing features
  • Prioritize by importance
  • Estimate effort
  • Create subtasks if needed

Code Locations

  • task web: Omni/Task/Web.hs, Omni/Task/Web/ (Components, Handlers, Pages, Style)
  • Studio: Omni/Agentd/Studio.hs

Output

  • Feature comparison table (filled in)
  • Prioritized list of improvements
  • Optionally: subtasks for each improvement

Execution

Could run via Designer workflow or create a custom investigator workflow:

echo "Compare task web (port 8090) vs Studio tasks (port 8091). 
Screenshot both, document features, produce improvement plan." | ./Omni/Agent/Workflows/Designer.md

Timeline (2)

💬[human]1 month ago

Agent stuck when trying to start DevBrowser (missing npm deps). Need to complete DevBrowser Python rewrite first (t-456).