[FEATURE] plugin-authored setting to suppress tool-call banners for non-technical end users
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I'm the author of a Claude Code plugin (distributed via a private marketplace) that ships a resolution-first workflow to non-technical support consultants. The plugin invokes internal skills (Skill(...)) and dispatches background sub-agents (Agent(...)) as normal parts of its pipeline.
The problem: for every skill call and every sub-agent completion, the harness renders chrome like:
● Skill(my-plugin:some-internal-skill)
Successfully loaded skill · 8 tools allowed · claude-sonnet-4-6
● 3 background agents launched (↓ to manage)
● Agent "Some sub-agent (round 1)" completed · 29s
These are meaningful to me as the plugin author. To a non-technical consultant they're visual noise — "8 tools allowed" and "claude-sonnet-4-6" are jargon they don't understand and can't act on. This came up as a real adoption blocker in a stakeholder demo this week: users saw the chrome and reported it as scary / confusing, ahead of any complaint about the plugin's own output. This is a real adoption blocker for plugins targeting non-developer audiences.
Proposed Solution
Ask: a setting (in settings.json or a plugin manifest field) to suppress tool-invocation banners while keeping the plugin's own rendered output. Something like:
{ "ui": { "hideToolBanners": true } }
Happy to iterate on the surface — user-level, project-level, or plugin-declared would all solve the problem. Even a boolean toggle would unblock adoption for this class of use case.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_