Customized Forbidden Command Message #6754
Description
What specific problem does this solve?
When agent tries to use a forbidden command, they are faced with a uninformative message like "This command is forbidden"
When the correct way of doing what agent is trying to do exists in rules, but it doesn't remember, they deviate.
Customized messages in these cases can help re orient the agent.
Additional context (optional)
Exampel case:
API/Frontend is actually running, but agent tries to initiate either anyway, ending in hung terminal and task flow is stopped. If command is forbidden, and agent doesn't remember rules that server is always running, they try other ways of running the server. A custom message can inform the agent automatically in these cases.
Roo Code Task Links (Optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear impact and context
Interested in implementing this?
- Yes, I'd like to help implement this feature
Implementation requirements
- I understand this needs approval before implementation begins
How should this be solved? (REQUIRED if contributing, optional otherwise)
No response
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
No response
Technical considerations (REQUIRED if contributing, optional otherwise)
No response
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
No response