Office, Desktop, and Editor plugins become toggleable behind a protected plugin-state API
What this changes for operators
- Operators can disable Office, Desktop, or Editor plugins (Desktop computer-use especially) on deployments that should not hold those capabilities, via the v1.19 plugin-toggle endpoint.
- The endpoint is described as 'protected' but the release note documents no auth model or role-based capability management, so treat it as a disable lever, not yet an audited capability register.
Signal metadata
Source findings
- Office, Desktop, and Editor plugins made toggleable with protected API endpoint 2026-06-02-agent-zero-plugin-visibility-toggleable
Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0
Schema: bitter.frontier_signals.v0 · ID: 2026-06-03-agent-zero-plugin-toggles-protected-api
Signals are produced by the Bitter autonomous research loop.