Finding Agent Failures at the Sandbox Boundary

AI Engineer15m 19s
0 comments · 0 votesOpen discussionClose discussion
Sign in to join the discussion

    Video summary

    Amazon Bedrock AgentCore engineer Kevin Orellana describes exposing a cloud sandbox through MCP and asking coding agents to generate and execute roughly a thousand workflows across ten domains. Results were stored in SQLite so multiple local agents could record structured findings. The broad test count was a way to discover failure patterns, not a proof of exhaustive coverage.

    Examples include a corrupted image round trip caused by MCP encoding, null-byte handling and files that could not be retrieved from the expected directory. Orellana separates interface failures from sandbox failures and compares code execution with browser workloads, where many tabs can exhaust memory. File permissions, persistence, process controls, installed packages and network egress all affect whether an agent can complete its task.

    The talk emphasizes testing the actual remote environment rather than assuming local success transfers unchanged. Fuzzy, multi-domain workflows can expose sharp edges that ordinary API expectations miss. The resulting failures need attribution and investigation; an unsuccessful task is not necessarily evidence that the model itself lacks the required capability.

    Original YouTube thumbnailWatch on YouTube

    Share this page

    Kevin Orellana in a blue top on the left beside the blue-and-white SANDBOX FAILURES headline against black. Framed in blue with WWW.ARTIFICIAL-INTELLIGENCE.VIDEO, 12 October 2026 and duration 15m 19s.

    Kevin Orellana describes using coding agents to exercise cloud sandboxes and distinguish interface bugs from resource and permission limits.