Skip to content

Agent: group sidebar tasks by status (failed, needs you, ready for review, running, idle) #1551

Open

Description

@w3irdrobot

Problem

With several tasks running across computers, the question I ask the sidebar is "what needs me next?". The row indicators already answer it per task (failed, waiting on an answer, finished unseen, running), but nothing sorts by them. Group tasks by → Status only splits Active from Settled, so the tasks that need attention are scattered through one long Active list and I have to scan for dots.

Paseo groups its agent list this way and it is the feature I miss most in Maple Work.

Proposal

This builds on #1521, which redraws the row indicators (a running row traces its outline, a task that needs you shows a coral dot in a halo) and gives each status a screen-reader label. It assumes #1521 lands first: the sections below group by exactly the statuses those indicators show, and the mockups use its indicators.

Replace the Active/Settled split of the Status grouping with sections ordered by urgency:

Order Section Contains Existing signal
1 Failed last run failed and I have not seen it SessionActivity::Failed
2 Needs you a question waits for my answer SessionActivity::NeedsYou
3 Ready for review a run finished and I have not seen it SessionActivity::CompletedUnread
4 Running a run is in progress SessionActivity::Running
5 Idle active, nothing pending, already seen no activity

Pinned stays above and Archived below, as today. Empty sections are hidden, and each section folds like Active and Settled do now.

Mockups, not screenshots of a build. Colours, type and icons are taken from theme.rs and the bundled assets; row indicators follow #1521's code (activity_indicator, outline_trace). The running trace is animated in the app, so each mockup shows one frozen frame of it.

Mockup to be attached: today's Status grouping beside the proposed one (dark).

Mockup to be attached: proposed Status grouping (light).

Behaviour

  • One list across computers. Tasks from this computer and every paired computer share the same sections; a row's second line keeps naming its project and computer. The Status grouping is already flat across computers, so this keeps that shape.
  • A task sits in exactly one section, picked by the precedence TaskActivity::of already uses: a waiting question outranks the run it paused, and a run outranks how the previous one ended.
  • Sections follow activity live. A task moves when a run starts, asks a question, or ends.
  • Read means seen in a focused window. Selecting a task in a focused window reads it straight away, and it moves to Idle. If a run ends on the selected task while the window is not focused, the task is unread (or failed) until the window is focused again. Today a run that ends on the selected task while the chat is showing is not marked, whether or not the window is focused.
  • Nothing that needs attention hides behind "Load more". Running tasks are already listed whatever page they fall on; failed, waiting and unread tasks get the same treatment.
  • Sort tasks by still applies inside each section. Manual order can reorder within a section, not between sections, since the section is derived.

Finding the option

The View options button already sits in the Projects header beside "add project", and already holds Group tasks by and Sort tasks by. It is invisible until the pointer is over the header, which is why I assumed the app had no such menu. I suggest showing it at rest.

Mockup to be attached: the View options menu with Status selected.

Where this touches the code

Anchors from master @ d53bd938, under apps/maple-agent/app/src/ui/chat/:

  • sidebar.rs: rebuild_sections partitions by session_is_active for SidebarGroup::Status; SidebarSection::{Active, Settled}; set_activity rebuilds sections only when running changes; view_button is hidden until the header is hovered.
  • sidebar_computers.rs: the paired-computer path builds the same Active/Settled sections.
  • sidebar_ordering.rs: TaskGroup::Status(bool) bounds drag reorder.
  • sidebar_prefix.rs, sidebar_paging.rs: paging by PageKind::{Active, Settled}.
  • mod.rs: completed_unread_sessions / failed_unread_sessions are set when a run ends unless visible && is_selected, with no check of window_active.
  • locales/*/app.ftl: section labels.

Related work

Out of scope

  • Keeping failed and unread markers across a restart. They appear to be in-memory on the chat screen today (restart behaviour not traced), so Failed and Ready for review start empty after a relaunch. Worth a follow-up.
  • Changing the Project, Connection, or list groupings.

Open questions

  • Section names: "Ready for review" or "Finished", "Idle" or "Active"?
  • Should section headings show a count, so a folded section still says how much is in it?
  • Should Status become the default grouping, or stay opt-in?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions