Python Guide
The Python SDK fits orchestration, ML-adjacent pipelines, and data-heavy application layers.
Primary surfaces
forge-py/src/forge/coreforge-py/src/forge/agentforge-py/src/forge/identityforge-py/src/forge/authforge-py/src/forge/mcp
Choose Python when
- your orchestration layer already lives in Python
- you need Forge concepts alongside data, automation, or ML workflows
- you value quick iteration without abandoning runtime structure
Use Python when you need
- orchestration in Python-centric systems
- integration into data or ML workflows
- fast iteration with strong typed runtime concepts
Baseline developer workflow
- start in
forge-py - run the package tests with the expected import path configuration
- keep provider, agent, identity, auth, and MCP flows aligned in application code
Useful verification commands
PYTHONPATH=src pytestpython3 tools/release_gate.py --root .
Current guidance
Keep public documentation honest about implementation status. Python support is tied to the same contract and release-gate expectations as every other SDK.