Finding / agent-zero

2026-10-13-agent-zero-remote-input-has-its-own-execution-capable-permission

Remote input has its own execution-capable permission ID. code_execution_remote no longer accepts runtime=input. The replacement input_remote dispatches runtime=terminal with framework-owned _allow_running=True. Running shells receive input; idle or missing shells execute the text as a command. Canonical policy IDs are matched independently, so blocking plugin:_a0_connector:code_execution_remote while leaving Tools default allow does not block plugin:_a0_connector:input_remote. It still requires the host connector’s exec and write grants. The local input tool also has a separate ID from code_execution_tool. Interactive CLI exec defaults off; ACP connection defaults differ (section 9).

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

Operator consequence: Block both remote execution/input IDs wherever host commands are forbidden, and both local IDs where local commands are forbidden; alternatively default Tools to block and allow deliberately. Verify denial through a subagent. Migrate old runtime=input scripts and upgrade the host CLI with the framework. The new chat namespace is state separation, not a permission fix.

Receipt

Finding metadata

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

Finding ID: 2026-10-13-agent-zero-remote-input-has-its-own-execution-capable-permission

Profile citations

Source links

Primary links, including exact changelog lines when available.