AWS released Strands Box, an open-source sandbox for AI agents whose rules weigh what an agent has already done before allowing its next action. Operators gain rules that can cap or sequence actions. They also take on more code to trust, by AWS's own account.
Perspective Coverage
3 publishers
- Builder
- Builder 45%
- Operator
- Operator 48%
- Investor
- Investor 7%
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+10
- Incentives50
- Confidence65
buildOne report1 publisher ShipStation reports its Deckhand agent resolved 97.5% of help desk channel queries
ShipStation Global says its Slack IT agent, Deckhand, resolved 97.5% of incoming channel queries and drew 96% positive feedback. Both figures are self-reported from one help desk channel, so they transfer only where answers already exist in writing.
Reality
- Evidence35
- Adoption25
- Hype gap+30
- Incentives75
- Confidence70
buildOne report1 publisher AWS, Upstage and Ollama adopt TypeSafe's System One schema for decision models
AWS, Upstage and Ollama now serve decision models through TypeSafe's System One request format, within three weeks of TypeSafe launching Jev. OpenAI has not signed on, so teams wiring decision calls into agents are picking an interface while the standard is still forming.
Reality
- Evidence55
- Adoption45
- Hype gap+15
- Incentives
- Not scored
- Confidence50
buildConfirmed2 publishers Zenity Labs found that one prompt to a single public Amazon Bedrock AgentCore agent could take over every agent in the same AWS account and region. Zenity says the partial fix from AWS still leaves teams to cut each agent's role down to minimal access by hand.
Reality
- Evidence50
- Adoption
- Not scored
- Hype gap+15
- Incentives65
- Confidence55
buildOne report1 publisher AWS adds seven objectives to the AI Practitioner exam guide five weeks after version 1.0
AWS published version 1.1 of the AIF-C01 AI Practitioner exam guide on April 30, five weeks after 1.0, with seven new objectives including token pricing. A dev.to review finds older courses still cover most of the exam but are thin on agents, token cost and grounding.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+5
- Incentives60
- Confidence55
AWS open-sourced Strands Decider 2B, a model that picks from a fixed list of options in under 150 milliseconds on a local machine, the company says. Agent builders get a small model they can run themselves for routing and tool-selection steps that would otherwise each call a full LLM.
Perspective Coverage
3 publishers
- Builder
- Builder 48%
- Operator
- Operator 25%
- Investor
- Investor 27%
Reality
- Evidence58
- Adoption
- Not scored
- Hype gap+22
- Incentives60
- Confidence62
buildOne report1 publisher Strands and CrewAI agents reported success on runs where verification never executed
Strands and CrewAI agents exited 0 on all six runs where a broken verification tool checked nothing, a recorded-proxy test on dev.to found. Only tool-call traffic captured outside the framework showed the failures.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+10
- Incentives
- Not scored
- Confidence40
buildOne report1 publisher Harsher tool-schema changes broke Strands, LangGraph and CrewAI in three different ways over 36 runs
Only a renamed tool argument got through Strands, LangGraph and CrewAI cleanly in a 36-run schema-change test posted on dev.to. Harsher changes let Strands and CrewAI exit 0 with nothing verified while LangGraph crashed outright, so each framework needs its own schema-change test.
Reality
- Evidence42
- Adoption
- Not scored
- Hype gap+12
- Incentives15
- Confidence40
buildOne report1 publisher HEMA wired its existing service catalog into Kiro and Claude as MCP tools
The AWS post co-written with HEMA says the structured half of its internal knowledge was already in good shape, and that the procedural half had little written documentation to fall back on.
Reality
- Evidence38
- Adoption42
- Hype gap+22
- Incentives78
- Confidence58
buildOne report1 publisher Tagging tool calls with source at write time turns the reverse audit into one traversal
A Strands hook recorder writes each agent step into Neo4j through Neo4j Labs' agent-memory SDK. The audit query that finds every decision touching a bad source depends on a dict lookup keyed by tool name.
Reality
- Evidence50
- Adoption
- Not scored
- Hype gap+20
- Incentives65
- Confidence55
buildOne report1 publisher Strands Harness keeps five subsystems local and routes one call to Bedrock
AWS has open-sourced a preconfigured general-purpose agent on top of its Strands SDK and says it runs 45% cheaper than Claude Code and Codex. The model call defaults to Amazon Bedrock, and Marc Brooker says one line changes that.
Reality
- Evidence50
- Adoption15
- Hype gap+25
- Incentives78
- Confidence45
buildOne report1 publisher Adding ChaosPlugin to a Strands agent injects tool failures without touching its code
Strands Evals 1.0 added chaos testing and red teaming in June. One AWS builder pointed both at a fixture-fed copy of his cost-reporting agent, because Cost Explorer charges a cent per API request.
Reality
- Evidence40
- Adoption15
- Hype gap+30
- Incentives55
- Confidence35
buildOne report1 publisher Sharing long-term memory across two agents comes down to the actorId you write under
A dev.to walkthrough gives a Nova Sonic voice agent and an Amplify AI Kit chat agent one long-term memory in Amazon Bedrock AgentCore Memory, where every record is filed under an actorId and a sessionId. Both channels already had short-term context.
Reality
- Evidence58
- Adoption12
- Hype gap+14
- Incentives52
- Confidence58
buildOne report1 publisher SageMaker's fallback instance can serve a quantized copy of the same model
AWS counted 13 SageMaker inference launches so far in 2026. The one that changes production behaviour most is a prioritized list of up to five instance types, each allowed its own model optimization settings.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+25
- Incentives85
- Confidence55
buildOne report1 publisher Wood Mackenzie consolidates three in-flight agent stacks onto one managed runtime
The company says 88 percent of its AI proofs-of-concept never reach widescale deployment, and it blames the identity, session and evaluation layers each team was rebuilding, so APEX builds them once on Amazon Bedrock AgentCore.
Reality
- Evidence34
- Adoption36
- Hype gap+28
- Incentives84
- Confidence52
buildOne report1 publisher MRH Trowe ran 400 employees on self-service agents for about $14 a seat in month one
AWS says the German insurance broker picked Bedrock AgentCore because it isolates every agent session at the compute and filesystem level, and points at right-sizing and scheduled scaling for the next 40 percent of infrastructure savings.
Reality
- Evidence42
- Adoption55
- Hype gap+28
- Incentives88
- Confidence45
buildOne report1 publisher Stage 1 of a Bedrock AgentCore migration cost 67 hand-written lines in one deployed PoC
A dev.to writeup deployed AWS's own migration sample, reran the repo's diff-checking script, and reports that the managed runtime, gateway and memory are worth taking while the LangGraph loop stays as written.
Reality
- Evidence63
- Adoption22
- Hype gap−8
- Incentives45
- Confidence60
buildOne report1 publisher Mixing self-hosted Qwen with Bedrock Claude costs you telemetry, not a rewrite
AWS shows three agents sharing one AgentCore container across two hosting paths. The orchestration framework absorbs the split; the OpenTelemetry instrumentation does not.
Reality
- Evidence74
- Adoption
- Not scored
- Hype gap+8
- Incentives86
- Confidence66
buildOne report1 publisher A poorly scoped supervisor prompt sends 20 percent of requests to the wrong specialist
An AWS post on agent monitoring describes failures that return clean responses and throw no exceptions, and answers them with a judge model that scores live interactions for helpfulness, correctness and goal completion.
Reality
- Evidence32
- Adoption15
- Hype gap+35
- Incentives88
- Confidence55
buildOne report1 publisher Renaming FastMCP to MCPServer closes stdio before an unpinned server finishes its handshake
An AWS EC2 rig with mcp unbounded in requirements.txt picked up mcp 2.2.0 and stopped importing. The server edit is two lines; the pip resolver and the test suite's camelCase attribute reads are where the work sits.
Reality
- Evidence72
- Adoption30
- Hype gap−8
- Incentives35
- Confidence68