Strands Agents SDK for TypeScript 1.15.0

Last reviewed Oct 28, 2026

Export as PDF

Prompt Details

Prompt Composition

4prompts
  1. JavaScript ES2026102 lines · 3.1K tokens
  2. Node.js 24101 lines · 5.3K tokens
  3. TypeScript 746 lines · 1.5K tokens
  4. Strands Agents SDK for TypeScript 1.15.079 lines · 3.6K tokens
Total328 lines · 13.5K tokens

CWE Coverage

  • 20
  • 22
  • 59
  • 73
  • 78
  • 79
  • 88
  • 89
  • 95
  • 113
  • 117
  • 200
  • 201
  • 208
  • 209
  • 214
  • 250
  • 295
  • 297
  • 306
  • 319
  • 323
  • 330
  • 338
  • 346
  • 347
  • 352
  • 354
  • 362
  • 367
  • 377
  • 426
  • 444
  • 459
  • 471
  • 488
  • 494
  • 502
  • 524
  • 532
  • 602
  • 639
  • 653
  • 732
  • 770
  • 807
  • 829
  • 838
  • 862
  • 863
  • 908
  • 915
  • 916
  • 918
  • 922
  • 942
  • 943
  • 1004
  • 1321
  • 1333
  • 1426
  • 1427

Prompt Preview

Apply the Node.js 24 and TypeScript 7 prompts first. These rules target @strands-agents/sdk 1.15.0 on Node.js 24; the package declares Node.js >=20.0.0. Use the TypeScript APIs for this release when configuring agents, tools, interventions, MCP, sessions, guardrails, and model routing.

Agents and instruction boundaries

  • Construct Agent with an application-owned systemPrompt, an explicit model, and only the tools needed for its role; treat plugins, middleware, hooks, and registry mutations as privileged application code.
  • Pass caller text as user content. Keep retrieved documents, memory, tool results, and agent messages distinct from trusted instructions; prompt delimiters and model compliance do not enforce authorization.
  • Build messages and snapshots from application-controlled history. Reject caller-supplied assistant, tool-use, tool-result, interrupt-response, and checkpoint structures at ordinary chat endpoints; persisted JSON is not trusted merely because it parses.
  • Use a separate agent and conversation namespace for each authenticated conversation. Keep current identity and authorization context in application-owned invocationState or a protected service context, outside model-selected tool arguments and memory.
  • Validate structuredOutput and final responses against business invariants before using them to select resources or cause effects; a successful Zod parse establishes shape, not permission or factual correctness.

Application output sinks

  • Treat AgentResult.lastMessage, structuredOutput, toString(), selected