-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
Problem (one or two sentences)
It's hard to tell when an execution is denied based on a rule. There's a green or red dot that appears next to the label "Running", which I believe is based on whether the command succeeded or failed.
But unless you're knowledgeable, the red dot doesn't mean it didn't run, but that it did run and execution failed (e.g. failed test run). This is confusing to me. Further, we don't get any dot when it did not run:
It even says "Running" which is false, as it was denied execution.
Context (who is affected and when)
Anytime automatic execution is enabled.
Desired behavior (conceptual, not technical)
I suggest, when execution is denied (automatically or manually), displaying a red X instead of a red/green dot, and changing the word "Running" to something else like "Running (denied)" or "Attempted run (denied)" or "Attempted execution (denied)" or something to indicate that the attempt was manually denied or automatically denied based on the configured rules.
Constraints / preferences (optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear context and impact
Roo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status