Skip to content

docs: add TypeScript vended tools documentation#685

Open
zastrowm wants to merge 3 commits intomainfrom
agent-tasks/671
Open

docs: add TypeScript vended tools documentation#685
zastrowm wants to merge 3 commits intomainfrom
agent-tasks/671

Conversation

@zastrowm
Copy link
Member

@zastrowm zastrowm commented Mar 19, 2026

Description

Adds a new "Vended Tools" documentation page for the TypeScript SDK covering the four built-in tools shipped with @strands-agents/sdk: bash, fileEditor, httpRequest, and notebook.

The page covers:

  • Quick start with import paths and basic agent setup
  • Per-tool descriptions with usage examples and security callouts where relevant
  • A combined multi-tool workflow example
  • A comparison table against the Python community tools package (consent model, tool count, platform support)
  • Versioning and maintenance expectations

Related Issues

Closes #671

Type of Change

  • New content

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

This comment was marked as outdated.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 19, 2026

Documentation Preview Ready

Your documentation preview has been successfully deployed!

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

Updated at: 2026-03-20T19:51:34.869Z

@zastrowm

This comment was marked as outdated.

@zastrowm

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

Add comprehensive documentation for TypeScript SDK vended tools:

- bash: Shell command execution with persistent sessions
- fileEditor: File viewing, creation, and editing
- httpRequest: HTTP requests to external APIs
- notebook: Persistent text notebooks

Includes:
- Security warnings and responsibility model documentation
- Code examples with TypeScript snippets
- Links to SDK READMEs for detailed API reference
- References to Interrupts/Hooks for consent workflows
- Navigation update to include page under Tools section
@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@zastrowm zastrowm added the agent label Mar 20, 2026
@zastrowm zastrowm marked this pull request as ready for review March 20, 2026 20:08
@zastrowm zastrowm enabled auto-merge (squash) March 20, 2026 20:15
--8<-- "user-guide/concepts/tools/vended-tools.ts:combined_tools_example"
```

## Differences from Community Tools
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I probably wouldn't mention the difference here. I like calling out interrupts for handling permissions, but we don't need the comparison here.

| Consent Workflow | Use Interrupts/Hooks | `BYPASS_TOOL_CONSENT` env var |
| Platform | Node.js (some browser support) | Python 3.10+ |

## Versioning & Maintenance
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For vended tools, what can we be expected to break in a patch or minor version bump? Tool name? Description? Spec?

Probably don't need to figure it out now, but adding a "version" to tools within the SDK might be nice so people who want a consistent tool spec can pin the tool version, or you can just choose latest for the most updated configuration.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[NEW CONTENT] Document TypeScript vended tools and the related guidance

2 participants