Strands Agents
You write the tools and the prompt; the model runs the loop and decides when it is finished
What is Strands Agents?
Strands Agents takes the opposite bet from the graph frameworks. You supply a system prompt and a handful of ordinary functions marked as tools, and the model decides which to call, in what order, and when to stop. A first agent is a few lines rather than a wiring diagram — and when a run goes somewhere odd there is no graph to point at, so you read the trace instead. Around that loop sit the pieces a long-running agent needs: hooks that fire at every step so you can log or refuse a tool call, conversation managers that trim or summarise history before it reaches the model's limit, and ways to hand one agent to another as a tool.
What can you do with Strands Agents?
- Turn a function into a tool with one decorator — Mark an ordinary function as a tool and the model can call it. The argument definition is generated from the type hints, so there is no separate schema to keep in step.
- Bring in tools from MCP servers — Point the agent at an MCP server and its tools sit alongside the ones you wrote, with no adapter code in between.
- Stop a tool call before it runs — Hooks fire at each stage of the loop, so you can record what is about to happen, rewrite the arguments, or refuse it outright.
- Keep a long conversation inside the window — Conversation managers drop or summarise older turns as the history grows, instead of letting a run fail once the model's input limit is reached.
- Let one agent call another — An agent can be handed to a second agent as a tool, or several can be run as a swarm that splits one task between them.
- See every decision as a trace — The loop emits OpenTelemetry spans, so the same tooling you already use for services shows which tools ran, in what order, and what they cost.
Before you choose Strands Agents
- The two languages are not at parity: the interrupt that pauses a run for a person's approval is documented for Python, with the TypeScript version listed as still to come.
- The defaults lean towards AWS — Amazon Bedrock is the assumed model provider and the deployment guides walk through Lambda, Fargate and EKS — although other providers and hosts are supported.
Star history
27 Aug to 30 Oct · +2k
Frequently asked questions
Is Strands Agents free for commercial use?
Strands Agents is released under the Apache-2.0 licence — OSI-approved open source, which permits commercial use.
How can Strands Agents be deployed?
Strands Agents is available as Self-hosted / Runs locally.