Strands Agents Samples
Practical Python and TypeScript examples for learning Strands Agents SDK patterns and deployment options.
- Source repo
- strands-agents/samples
- Stars
- ★ 852
- Last updated
- 22d ago
- License
- Apache-2.0
- Primary language
- Python
- FA score
- 40/100 · Major gaps
At a glance
- Works with
- Platform-specific
- You'll need
- Typical use
- A Python developer who wants to validate a first Agent invocation before moving on to SDK fundamentals, streaming, or multi-agent systems.
- Main limitation
- The repository explicitly says the examples are for demonstration and education, not direct production use; adopters must add security controls and testing.
- Source review
- 40/100 · Major gaps 1 safety controls not found
What does this agent do, and when should you use it?
Strands Agents Samples is a Python and TypeScript example repository built around the Strands Agents SDK. Its Python collection covers SDK fundamentals, multi-agent systems, streaming, deployment, integrations, industry examples, technical patterns, evaluation, UX demos, and edge-device work. The TypeScript collection includes SDK tutorials and AgentCore deployment patterns. The minimal examples construct an Agent, send it a prompt, and print the returned response to the console. The repository explicitly positions every example as educational and demonstrative, so production users must add their own security and testing practices.
After model-provider and model-access setup, a developer installs strands-agents and strands-agents-tools for Python, or @strands-agents/sdk for TypeScript. The Python starter imports Agent from strands, creates agent = Agent(), calls agent("Hello! Tell me a joke."), and prints response. The TypeScript starter imports Agent from @strands-agents/sdk, creates it with systemPrompt, calls await agent.invoke("Hello! Tell me a joke."), and logs response.toString(). Repository directories also organize patterns for Lambda, Fargate, and AgentCore deployment, plus examples concerning AWS services, databases, third-party tools, evaluations, and UI applications.
- A Python developer who wants to validate a first Agent invocation before moving on to SDK fundamentals, streaming, or multi-agent systems.
- An engineering team looking for reference patterns when considering Strands Agents on AWS Lambda, Fargate, or AgentCore.
- An integration developer exploring examples that combine an agent with AWS services, databases, or third-party tools.
- A prototyping team in finance, healthcare, retail, or productivity that wants to start from industry-organized examples.
- A technical practitioner investigating Agentic RAG, evaluation tutorials, testing patterns, or full-stack UI demonstrations.
- A developer exploring edge-device, physical-AI, or robotics integration examples.
How do you install or deploy this agent?
Python requires Python 3.10+ and pip. Create and activate a virtual environment:
python -m venv venv
source venv/bin/activateThen install:
pip install strands-agents strands-agents-toolsTypeScript requires Node.js 18+ and npm or yarn. Install:
npm install @strands-agents/sdkBoth paths require model-provider and model-access configuration first. The supplied material does not specify credential names, environment variables, or configuration commands.
How do you use this agent?
First Python invocation:
from strands import Agentagent = Agent()
response = agent("Hello! Tell me a joke.")
print(response)First TypeScript invocation:
import { Agent } from "@strands-agents/sdk";
async function main() {
const agent = new Agent({
systemPrompt: "You are a helpful assistant."});
const response = await agent.invoke("Hello! Tell me a joke.");
console.log(response.toString());
}
main();
Configure model-provider and model access before running either example; the supplied material does not include copyable configuration steps.
What are this agent's strengths and limitations?
- Provides minimal Agent invocations in both Python and TypeScript, making it easy to validate SDK usage from either stack.
- Organizes Python examples across learning, deployment, integration, industry, evaluation, UX, and edge-device tracks.
- Names concrete deployment directions for Lambda, Fargate, and AgentCore, plus AWS-service, database, and third-party-tool integrations.
- Covers specific subjects including multi-agent systems, streaming, Agentic RAG, and evaluation/testing rather than only a chat example.
- The repository explicitly says the examples are for demonstration and education, not direct production use; adopters must add security controls and testing.
- Model-provider and model-access configuration is required, but the supplied material does not document exact credentials, environment variables, or commands.
- This is a Strands Agents SDK sample collection rather than a standalone end-to-end agent product; business workflows, data sources, and production operations remain implementation work.
- The documented Python and TypeScript coverage is uneven: the supplied material lists only learning and AgentCore deployment tracks for TypeScript.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|
| Strands Agents Samples This agent | 40 · Major gaps | ★ 852 | 22d ago | Python | — |
| HUD | 63 · Some gaps | ★ 302 | 4d ago | Python | OpenAI API · Claude API |
| PenguinHarness | 52 · Major gaps | ★ 2.3k | 5d ago | TypeScript | OpenAI API · Claude API |
| Hindsight | 46 · Major gaps | ★ 27k | today | Python | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows security scan workflows and tests, but no explicit documentation on least privilege, user confirmation, data flow transparency, sensitive data handling, dependency security, external effects, or rollback. Deductions: lack of specific security design documentation and permission analysis.
Unit tests exist, but no detailed dependency availability guarantees or failure message documentation. Deductions: limited test coverage and unclear dependency management.
README provides multiple scenarios and examples, but capability boundaries and trigger precision are not clearly defined. Deductions: lack of detailed description of agent capability limits and trigger conditions.
Has README, installation instructions, and examples, but lacks version changelog and detailed known limitations. Deductions: unclear version management and maintenance responsibility.
Examples show practical use, but no quantitative analysis of output usability, marginal value, or cost-benefit. Deductions: lack of performance evaluation and cost data.
Tests and documentation exist, but no evidence of claim traceability, cross-source corroboration, or separation of facts and inferences. Deductions: lack of verifiable claim sources.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- The repository does not provide explicit least privilege or user confirmation mechanisms; evaluate before production use.
- Dependency security is not clearly documented; check requirements.txt for dependency versions and known vulnerabilities.
- No version changelog, making it difficult to track update history.