forge docs

TypeScript Tools

This page shows Tools from the TypeScript SDK perspective. The shared Forge contract still applies, but examples, package boundaries, verification commands, and deployment expectations should be read through browser, Node.js, Deno, Bun, app shells, and agent-facing UI.

Language context

  • Primary package surface: @forge/sdk
  • Install entry point: npm install @forge/sdk
  • Verification command: npm test && npm run build
  • Shared contract reference: Tools

TypeScript should feel application-native, but browser ergonomics do not weaken identity, capability, or telemetry rules.

Subject in TypeScript

For TypeScript, focus on tool tiering, approval policy, typed arguments, runtime errors, and audit evidence. Treat this page as the language-specific entry point, then use the shared contract page when you need the cross-language rule text.

Implementation checklist

  1. Start with the TypeScript package boundary rather than copying examples from another SDK.
  2. Keep OAS identity and Arsenal capability checks visible in the code path.
  3. Use provider names through Forge's namespace contract instead of hard-coding vendors.
  4. Run npm test && npm run build before claiming behavior is ready.
  5. Run python3 tools/release_gate.py --root . before release work.
npm install @forge/sdk
npm test && npm run build