Resources and Update Tracking
Resources and Update Tracking
Section titled “Resources and Update Tracking”Where to look
Section titled “Where to look”| Need | Resource |
|---|---|
| Install and first run | Docs / PyPI |
| Source and issues | Repository |
| Fast index | llms.txt |
Keep local notes to project decisions: version pin, provider, enabled workflow, tool contracts, output schema, deployment, and rollback.
Use resources by question type
Section titled “Use resources by question type”Official docs are best for supported behavior. Package metadata is best for requirements. Source code is best for exact implementation. Issues are useful for symptoms and edge cases.
| Need | Start with |
|---|---|
| Install or version requirement | PyPI package |
| Supported usage | Official docs |
| Implementation detail | Repository source. |
| Recent rough edges | Repository issues and changelog. |
Keep local notes short
Section titled “Keep local notes short”Project notes should record decisions: version pin, provider, enabled workflows, tool contracts, output schema, deployment path, and rollback. Do not mirror an entire official docs site.
Related pages
Section titled “Related pages”References
Section titled “References”- Official docs: https://docs.swarms.world/
- Repository: https://github.com/kyegomez/swarms
- LLM docs index: https://docs.swarms.world/llms.txt
- PyPI package: https://pypi.org/project/swarms/