Guides
Use the guides section when you want help making progress, not just to look up definitions.
These pages are written as paths through the framework:
- how to get the runtime working the first time
- how to make good configuration decisions
- how to extend the system safely
- how to apply the framework to real Salesforce workflows
- how to debug and recover when something behaves unexpectedly
Onboarding Implementation Operations
How To Use This Section
Most teams should not read the guides in random order.
The shortest productive path is:
- Read
Getting Startedto make the core runtime work once. - Read
Configurationto understand what behavior is controlled by metadata and settings. - Read
Use Casesto choose a realistic first pattern instead of building a vague all-purpose agent. - Read
Developer Guideonly when configuration is no longer enough. - Use
Troubleshootingwhen runtime behavior, permissions, or tool choice does not match expectations.
Reader Paths
What The Guides Assume
The guides assume you want to work with the core runtime in force-app, not internal addon-only
authoring surfaces.
They also assume you care about production behavior, not just demos. That means the guidance leans toward:
- narrower first use cases
- explicit approval and trust controls
- predictable tool contracts
- observability through execution, step, session, and message records
What This Section Is Not
The guides section is not a full API contract reference and not a class-by-class code walkthrough.
When you need vocabulary, public contracts, or deeper conceptual grounding, move into the
Reference section next.