Strands Agents: building AI agents with the AWS SDK
Strands Agents is an open source development kit from Amazon Web Services for building AI agents in Python or TypeScript, with whichever model you prefer. It targets developers who want a simple, controllable agent loop rather than a heavyweight framework.
Data as of October 22, 2026
Key figures
| Developer | Amazon Web Services (AWS) |
|---|---|
| Type | Code |
| Languages | Python, TypeScript |
| Open source | Yes |
| License | Apache-2.0 |
| First release | May 2025 |
| Suggested level | Intermediate |
| Use cases | multi-agent, workflows, automation |
| Self-hostable | Yes |
| Business model | Free |
| Cloud offering | No |
| Multi-agent | Yes |
| MCP support | Yes |
| Bring your own model | Yes |
| Official site | Official site · Documentation · Repository |
GitHub
| Repository | strands-agents/harness-sdk |
|---|---|
| GitHub stars | 8,913 |
| Forks | 1,407 |
| Latest code activity | October 22, 2026 |
| Latest release | typescript/v1.22.0 (October 21, 2026) |
GitHub activity checked on October 22, 2026.
An SDK born inside Amazon
AWS introduced Strands Agents in May 2025 as a tool that came out of its own teams, who were using it internally to build AI agents. Its philosophy is “model-driven”: instead of describing every step in a graph, you give the agent instructions, a model and a list of tools, and the model decides when to call which tool (tool calling). The SDK handles the rest: the execution loop, turn and token limits, streaming, structured output, memory, sessions and tracing.
In 2026 the project was reorganized into a single repository that holds the Python SDK, the TypeScript SDK, a command-line tool and the “Strands harness”, a ready-to-use, pre-assembled agent.
Who is it for, and what for?
Strands is aimed at developers who would otherwise write their own agent loop. Typical uses: an internal assistant that queries company APIs, an analysis agent that chains searches and calculations, or a multi-agent system where several specialists split a task. The AWS connection is a plus for teams already on Bedrock, but the SDK stays provider-neutral and connects to MCP servers.
Getting started
You need Python 3.10 or later, or Node.js 22 or later. The fastest route is to install the harness package and call a single agent-creation function. If you want full control, install the strands-agents SDK instead, create an agent object with your tools, then configure the model provider and its credentials (an API key or AWS access). The official quickstart walks through each provider.
Strengths and limitations
Strengths: a short API, two languages, model independence, production features built in (tracing, guardrails, evaluations) and a permissive license.
Limitations: the project moves fast and its structure has changed (renamed repositories, a new harness), so some tutorials may be out of date. Many examples assume an AWS account. As with any agent, every run consumes tokens: estimate the bill with the agent cost calculator.
Alternatives
LangGraph is a better fit if you want to define each step precisely, the OpenAI Agents SDK and Google ADK fill the same role for other model makers, and Pydantic AI focuses on strict typing in Python.
Frameworks of the same type
- CrewAI · multi-agent, automation, workflows
- Agno · multi-agent, workflows, RAG
- Amazon Bedrock Agents / AgentCore · multi-agent, RAG, workflows
- Atomic Agents · workflows, chatbot, automation
- BeeAI Framework · multi-agent, workflows, RAG
- CAMEL · multi-agent, data, automation
Frequently asked questions
Do I have to use AWS with Strands Agents?
No. The SDK works with Amazon Bedrock, but also with Anthropic, OpenAI, Gemini, Ollama and other providers. It runs inside your own program, with no mandatory hosted service. Just note that the TypeScript SDK defaults to Bedrock if you don't specify a model.
Is Strands Agents free?
Yes, the code is released under the Apache 2.0 license. What you pay for is model usage with your chosen provider and, if needed, hosting for your agent, for example on AWS services that are billed separately.
What is the difference between the harness and the SDK?
The harness is a pre-assembled agent with default settings for the model, tools, memory and context, created with a single function call. The SDK is the layer underneath, for developers who want to write their own agent loop and configure everything.
Can several agents work together?
Yes. The documentation describes several multi-agent patterns built into the SDK, plus support for the Model Context Protocol to plug in external tools.
Data sources
- github.com
- strandsagents.com
- aws.amazon.com
- GitHub — Repository metadata: GitHub
Data as of October 22, 2026
Report an error
Does a figure, a date or a fact look wrong? Tell us: every report is checked.