bench: orchestrator / agent spawn runtime#2
Conversation
AntFleet · 3 findingsBoth reviewers flagged the items below on the changed files. AntFleet posts only what two independent frontier models agree on. Security · High — Bash guard strips executable command substitutions before checking denied git ops
Fix: Do not strip echo/printf/heredoc text until after parsing enough shell syntax to distinguish literal data from expansions, or add a conservative pre-check that denies git deny-list patterns inside Data-loss · High — Transcript retention can prune non-agent sessions with matching path prefixes
Fix: Match only the exact root or children under the root, e.g. compare against Security · Medium — Orchestrator lifecycle routes have no visible authorization guard
Fix: Require an admin/service credential or explicit role check on these endpoints. If protection is supplied globally, add a local dependency or code comment/test that asserts this router is mounted behind that protection so future refactors do not expose it accidentally. — Review |
Manual file pick from rennf93/roboco — runtime spawn manifest, agent_sdk drivers/server, orchestrator HTTP route, bash-guard hook (9 files, ~81KB).
Note: runtime/orchestrator.py (360KB) exceeds review-gate per-file cap and is excluded.
Two-model security review (Claude Opus 4.7 + GPT-5).
Methodology: https://github.com/AntFleet/bench-roboco