Skip to content

Expose monitoring waits to sidebar plugins #3441

Description

@yusuf8834

Problem

A sidebar extension cannot distinguish an agent that is monitoring a long-running task from an agent doing ordinary work.

During a real monitor wait, PluginSidebarThread reports:

  • indicator: runtime
  • indicatorLabel: Thread working
  • thread status: active

The thread event log contains the underlying pending command execution, but no event or field for the monitor wait itself. An extension therefore cannot display Monitoring without guessing from message text, elapsed time, or the command.

Request

Expose the monitor state to thread-list plugins. Either of these would work:

  1. Add a monitoring indicator to PluginSidebarThreadIndicator.
  2. Keep the runtime indicator and set indicatorLabel to Thread monitoring while the provider is in a monitor wait.

A stable boolean or runtime substate would also work and would be clearer than parsing a human-readable label.

Reproduction

  1. Install a plugin that replaces the thread list.
  2. Start an agent turn that launches a long-running command.
  3. Have the agent enter its monitor or wait state.
  4. Inspect the PluginSidebarThread value and thread event log.

Expected: the plugin receives a distinct monitoring signal.

Actual: the plugin receives the same runtime and Thread working values as ordinary active work.

The bb-sidebar extension already has display support for a Thread monitoring label and can show Monitoring with the existing elapsed-time treatment once BB supplies the state.

AGENT GENERATED

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

    pluginsPlugin SDK, runtime, marketplace

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions