Finding / agent-zero

2026-10-13-agent-zero-messaging-users-can-toggle-plugins-and-edit-project-scoped-profile-permissions

Messaging users can toggle plugins and edit project-scoped profile permissions. Telegram and WhatsApp run incoming messages through the shared Commands catalog before the agent sees them. /plugins changes toggles instance-wide, protecting always-enabled plugins, Commands and the integration itself; it can disable the opt-in _infection_check. /permissions refuses the built-in Default profile and active runs, then writes through Agent Editor. The change persists in that profile’s active project scope, or its global scope when no project is active; chats resolving that scope can inherit it. /copy exports the bound transcript. Telegram /chat accepts an arbitrary instance chat ID and its picker lists all contexts; WhatsApp checks conversation ownership. Empty Telegram allowed_users and WhatsApp allowed_numbers admit every sender once configured. Telegram numeric IDs match account IDs; @name entries match the current username. Both integrations ship unconfigured, not as active public bots. Computer Use grants stay at the host bridge.

Channel: tagged-release. Half: both. Date: 2026-09-23 (first stable; implementation 2026-09-14).

Operator consequence: Before upgrading a configured bot or pairing, set explicit numeric allowed_users or allowed_numbers. Treat admitted identities as plugin administrators and as policy editors for non-Default profiles/scopes they can reach. Check both the saved project scope and plugin toggles after messaging use. A non-allowed account should receive no /permissions response; an allowed account should reach the menu. That live acceptance test remains to be performed.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-agent-zero-messaging-users-can-toggle-plugins-and-edit-project-scoped-profile-permissions

Profile citations

Source links

Primary links, including exact changelog lines when available.