What changed
The documentation for the Strands Agents SDK, which facilitates building AI agents with a model-driven approach, has been moved. The original repository, strands-agents/docs, is now archived. All documentation source code is now located within the site/ directory of the new monorepo, strands-agents/harness-sdk. Future development, issue tracking, and pull requests for the SDK's documentation should be directed to this new repository.
Key aspects of the move:
- Archived Repository: The strands-agents/docs repository is no longer the primary location for documentation. It is marked as archived.
- New Monorepo: The documentation is now part of the strands-agents/harness-sdk monorepo.
- Source Code Location: Documentation source files are found under the site/ directory within the new monorepo.
- Development Focus: All new contributions, bug reports, and feature requests related to the documentation should target strands-agents/harness-sdk.
The documentation site itself is built using Astro with the Starlight theme and provides guides, samples, API references, and information on the Python SDK, tools, agent builder, and MCP server. The official documentation is accessible online at https://strandsagents.com.
For local development, prerequisites include Python 3.10+ and Node.js 20+ with npm. Installation involves running npm install. Building the static site is done via npm run build, and a local development server can be started with npm run dev.
Documentation content is written in Markdown files within the docs/ directory. The site structure is managed by src/config/navigation.yml. The documentation process includes specific skills for writing (/docs-writer), reviewing (/docs-reviewer), and planning (/docs-planner). These can be chained using a /goal directive to automate updates based on SDK changes, such as linking a commit to a documentation update workflow.
Why it matters for builders
Developers utilizing the Strands Agents SDK need to be aware of this repository change to access up-to-date documentation. The consolidation into a monorepo suggests a move towards a more integrated development experience, potentially simplifying dependency management and code sharing between the SDK and its documentation.
Practical impact
Builders should update any bookmarks or references pointing to the old strands-agents/docs repository. For new contributions or issue reporting related to the SDK's documentation, all interactions must now occur within the strands-agents/harness-sdk repository. Familiarizing oneself with the local development setup for the new monorepo will be necessary for contributing to the documentation.
Caveats and source limits
The provided source indicates the documentation repository has been archived and moved. It does not specify the exact date of the move beyond the published date of the repository's metadata. The source also does not detail any changes to the SDK itself, only the location of its documentation. The specific version of the SDK associated with this documentation is not explicitly stated, though the latest release mentioned for the documentation repository is v0.1.0. The source does not provide performance benchmarks or pricing information for the Strands Agents SDK.
Sources
Claim check: 5/5 supported claims - 5 evidence links - 100% avg confidence
- The Strands Agents SDK documentation repository has been archived and moved to the strands-agents/harness-sdk monorepo.supported - github.com
- All new development, issues, and pull requests for the Strands Agents SDK documentation should now be directed to the strands-agents/harness-sdk monorepo.supported - github.com
- The Strands Agents SDK documentation is built using Astro with the Starlight theme.supported - github.com
- Local development for the documentation requires Python 3.10+ and Node.js 20+ with npm.supported - github.com
- The Strands Agents SDK documentation is licensed under the Apache License 2.0.supported - github.com
Caveats
- This is based on the repository's archived status and explicit mention of the move within its README.
- This is stated directly in the archived repository's README.
- This information is provided in the documentation's README.
- These prerequisites are listed in the local development section of the documentation.
- This license information is provided in the repository's README.
- Single-source caution: verify critical details at the linked source.
Radar score 73/100 - how it was calculated
- Reliability 82: GitHub metadata supports source trust
- Freshness 8: Fresh GitHub release date
- Novelty 55: Novelty blends source metadata and enrichment
- Technical 73: Repository technical metadata
- Developer 94: Developer tooling signals
- Ecosystem 66: Developer-oriented GitHub signal
- Confidence 100: Claims have reliable evidence