TypeScript Guide

The TypeScript SDK provides Forge surfaces for browser and Node.js environments.

Primary surfaces

• forge-ts/packages/forge-core
• forge-ts/packages/forge-agent
• forge-ts/packages/forge-identity
• forge-ts/packages/forge-auth
• forge-ts/packages/forge-mcp

Choose TypeScript when

• you are building application-facing web integrations
• you need Node.js or browser-oriented orchestration
• you want Forge concepts inside a TypeScript application stack

Use TypeScript when you need

• application-layer orchestration in web stacks
• browser or Node.js integrations
• SDK aggregation through the TypeScript package surface

Baseline developer workflow

1. start in forge-ts
2. verify package tests and build health
3. read the package boundaries instead of assuming one flat SDK surface
4. keep provider, identity, auth, and agent contracts aligned in your app code

Useful verification commands

• npm test
• npm run build
• python3 tools/release_gate.py --root .

Current guidance

Use the same contract model as Rust. Production status for any given surface is defined by the release gate, not by package presence alone.