Studio brings the full agent lifecycle into one workspace. The pattern: open Studio, build the agent in Agent Builder, author needed Prompt Templates in Prompt Builder, pick a model in Model Builder, test in Testing Center, publish to a channel.
- Open Agentforce Studio
Setup, Quick Find, Agentforce Studio. The workspace lists every agent in the org plus links to Agent Builder, Prompt Builder, Model Builder, and Testing Center. Pick an existing agent or create a new one.
- Build or refine the agent in Agent Builder
Define Topics, attach Actions, write Instructions. Use the inline Test panel to validate behaviour as you build. Save the draft version frequently; Studio supports versioned drafts so you can roll back if needed.
- Author Prompt Templates as needed
For content-generation Actions, open Prompt Builder. Author the prompt with input variables, instructions, grounding references. Test the template in Prompt Builder before attaching to the agent.
- Configure the LLM in Model Builder
Pick the model per agent or per Topic. Atlas Reasoning Engine is the default; switch to GPT or another supported model if the use case warrants. Trust Layer applies consistently across models.
- Test in the Agentforce Testing Center
Build a test suite per Topic. Run the suite. Review failures and iterate on Agent Builder until pass rates are acceptable. Activate and deploy to a channel.
Agent Builder, Prompt Builder, Model Builder, Testing Center, monitoring dashboard. Pick the tool per task within the integrated workspace.
Atlas Reasoning Engine (default), GPT, Anthropic Claude, other supported models. Trade cost, latency, capability per use case.
Run the test suite before every deployment. Continuous testing (every save) catches regressions earlier than gate-only testing.
Studio manages versioned drafts per agent. Activate, rollback, or compare versions from the workspace.
- Studio is the build workspace, not the runtime. Agents run on the Agentforce platform after deployment; Studio is admin-facing only.
- Switching the underlying LLM mid-development can change agent behaviour subtly. Re-test after model switches before assuming behaviour is preserved.
- Testing Center coverage matters. Agents that pass shallow tests still fail in production; build deep test suites including adversarial cases.
- Channel deployment is per-version. Activating a new agent version in Studio updates the channel runtime; coordinate with operations before changing production agents.
- Studio updates frequently with Agentforce releases. Documentation can lag the UI; reference the current Salesforce Help when in doubt.