Amazon Bedrock AgentCore Code Interpreter vs Offscreen

Amazon Bedrock AgentCore Code Interpreter

Each session runs in its own microVM with 2 vCPU, 8 GB and a 10 GB disk for up to eight hours, and IAM can scope access to one interpreter. Sessions cannot be paused or resumed, and an AWS account with IAM set-up is needed before a first call.

Offscreen

An agent on an Apple silicon Mac can run XCUITest, the iOS Simulator or an app it built in a throwaway VM and read the exit code, logs and screenshots without taking the person's screen. The project is six days old at v0.0.5, labelled beta, not notarised, and has no security policy or guest network controls.

Amazon Bedrock AgentCore Code Interpreter

1. Start a session with StartCodeInterpreterSession, then pass its id in the x-amzn-code-interpreter-session-id header on every InvokeCodeInterpreter call
2. Set sessionTimeoutSeconds when starting. The default is 900 seconds and the maximum is eight hours, and the session ends itself at the timeout
3. Stop sessions when done. Billing runs per second while code is busy, and a session left open counts against the 1,000 concurrent-session quota
4. Use bedrock-agentcore 1.18.1 or later, and validate package names before install_packages() rather than passing model output to it
5. Retry ThrottlingException (429) and InternalServerException (500) with exponential backoff, and treat ServiceQuotaExceededException, returned as HTTP 402, as a quota to raise

Offscreen

1. Read .offscreen.toml before running anything and use its project key and task names. Don't guess them
2. Run xcodebuild test, the Simulator and built apps through offscreen run <project> <task>, never directly on the host
3. Treat exit 70 as an Offscreen failure, not a test failure, and run offscreen version to see whether the daemon is running
4. Ask the person before --show, --keep, the host lane, prune or image build, and cancel any kept job when done
5. Read screenshots and .xcresult bundles from the directory offscreen artifacts <job> prints