blog: How We Built the TypeScript SDK Using GitHub-Based Agents#742
Open
Unshure wants to merge 2 commits intostrands-agents:mainfrom
Open
blog: How We Built the TypeScript SDK Using GitHub-Based Agents#742Unshure wants to merge 2 commits intostrands-agents:mainfrom
Unshure wants to merge 2 commits intostrands-agents:mainfrom
Conversation
Contributor
Documentation Preview ReadyYour documentation preview has been successfully deployed! Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-cms-742/docs/user-guide/quickstart/overview/ Updated at: 2026-04-10T21:48:38.318Z |
Contributor
Documentation Preview FailedThe documentation deployment encountered an error. Please check the deployment logs for more details. |
Unshure
force-pushed
the
Unshure/research-strands-agents
branch
from
bd3b856 to
214b994
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
src/content/authors.yaml
Outdated
| @@ -1,3 +1,8 @@ | |||
| - id: nick-clegg | |||
Contributor
There was a problem hiding this comment.
✅ Resolved — the branch has been rebased onto the latest main. The nicholas-clegg and james-hood author entries are now present, and the diff is clean (only the new blog post file).
Contributor
|
Assessment: Approve All previously flagged issues (duplicate author entry, branch behind Review Details
|
Adds a blog post covering how the Strands team used agent SOPs and GitHub-based AI agents (refiner/implementer) to build the TypeScript SDK, and adds nick-clegg as a blog author. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Unshure
force-pushed
the
Unshure/research-strands-agents
branch
from
214b994 to
5667e6b
Compare
Contributor
|
Assessment: Approve Re-reviewed after rebase. No new issues found — the PR is clean and ready to merge. Review Details
|
Unshure
force-pushed
the
Unshure/research-strands-agents
branch
from
5667e6b to
b47eaa4
Compare
| @@ -0,0 +1,104 @@ | |||
| --- | |||
| title: "How We built Strands Typescript SDK with Strands Agents" | |||
Contributor
There was a problem hiding this comment.
Issue: The title has inconsistent capitalization — "How We built Strands Typescript SDK with Strands Agents". Other blog posts in this repo use proper title case and the correct product name casing.
Suggestion:
title: "How We Built the Strands TypeScript SDK with Strands Agents"
Note: "TypeScript" (capital S) is the official product name, and "Built" should be capitalized in title case.
|
|
||
| One of the [most requested features](https://github.com/strands-agents/sdk-python/issues/156) to the Strands team was to add support for running Strands in TypeScript. A feature request like this was expected, TypeScript and JavaScript together topped popular leaderboards as the most used language by developers in 2025 ([github](https://github.blog/news-insights/octoverse/octoverse-a-new-developer-joins-github-every-second-as-ai-leads-typescript-to-1/), [stack overflow](https://survey.stackoverflow.co/2025/technology#most-popular-technologies-language-language)). | ||
|
|
||
| As the team was considering this feature, we wanted to reflect on our experience of building the Strands Python SDK, and the challenges we faced. The Python codebase started as a passion project among some of the early engineers in the team, and was developed with the help of Coding Agents written by that very same codebase! These Agents were powered by models released in mid-2024 (think Claude 3.5) which were not nearly as capable as models we have available to us today. The LLM's of that generation were not known for their code quality, and lead to the reputation around "Vibe-Coding" we all know so well today, so its easy to understand that they required a lot of oversight in order to produce good results. |
Contributor
There was a problem hiding this comment.
Issue: A few grammar issues in this paragraph:
"LLM's"→"LLMs"(no apostrophe for plurals)"lead to"→"led to"(past tense needed)"its easy"→"it's easy"(missing contraction)
Suggestion:
The LLMs of that generation were not known for their code quality, and led to the reputation around "Vibe-Coding" we all know so well today, so it's easy to understand that they required a lot of oversight in order to produce good results.
Contributor
|
Assessment: Comment The rewritten introduction adds good context (feature request link, survey data, image). A few grammar and capitalization issues in the new content need a quick pass before merging. Review Details
|
|
|
||
| As the team was considering this feature, we wanted to reflect on our experience of building the Strands Python SDK, and the challenges we faced. The Python codebase started as a passion project among some of the early engineers in the team, and was developed with the help of Coding Agents written by that very same codebase! These Agents were powered by models released in mid-2024 (think Claude 3.5) which were not nearly as capable as models we have available to us today. The LLM's of that generation were not known for their code quality, and lead to the reputation around "Vibe-Coding" we all know so well today, so its easy to understand that they required a lot of oversight in order to produce good results. | ||
|
|
||
| Looking forward to the development of a new SDK, we wanted to learn from our lessons and utilize agent to write code **better** and **faster**. |
Contributor
There was a problem hiding this comment.
Issue: Minor grammar — "utilize agent to" should be "utilize agents to" (plural).
Suggestion:
we wanted to learn from our lessons and utilize agents to write code **better** and **faster**.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nick-cleggas a blog author inauthors.yamlTest plan
npm run build/blog/how-we-built-typescript-with-agents/🤖 Generated with Claude Code