Skip to content

feat: deploy strands design doc#711

Open
afarntrog wants to merge 2 commits intostrands-agents:mainfrom
afarntrog:deploy_strands
Open

feat: deploy strands design doc#711
afarntrog wants to merge 2 commits intostrands-agents:mainfrom
afarntrog:deploy_strands

Conversation

@afarntrog
Copy link
Copy Markdown
Contributor

Description

Design doc proposing adding a built in frictionless approach to deploying strands agents

Related Issues

Type of Change

  • New content
  • Content update/revision
  • Structure/organization improvement
  • Typo/formatting fix
  • Bug fix
  • Other (please describe):

Checklist

  • I have read the CONTRIBUTING document
  • My changes follow the project's documentation style
  • I have tested the documentation locally using npm run dev
  • Links in the documentation are valid and working

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 26, 2026

Documentation Preview Ready

Your documentation preview has been successfully deployed!

Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-cms-711/docs/user-guide/quickstart/overview/

Updated at: 2026-03-31T14:21:05.206Z

@afarntrog
Copy link
Copy Markdown
Contributor Author

afarntrog commented Mar 26, 2026

From my discussion with Owen:

the starter kit will be deprecated so we should consider extracting out the core runtime deploy logic

- cut corners by scoping it strands
- update the Result object to have a an invoke with boto: result = deploy(agent), result.invoke()
- maybe copy out some of the core functionality from the toolkit since it's being deprecated

Add a new section to the deploy design document (0004) proposing an
alternative approach that places deployment functionality in the
strands-agents-extensions package as a `DeployableAgent` wrapper class
instead of in the core SDK. Includes motivation, implementation sketch,
delegation details, packaging considerations, and a comparison table
between the two approaches with a recommended path forward.
@afarntrog
Copy link
Copy Markdown
Contributor Author

From my discussion with Nick:

consider moving this into a separate package

update the design doc with another approach. See the DeployableAgent idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants