SF Pi Quickstart
After installing SF Pi, use these commands to confirm the package is loaded and to discover the surfaces available in your current pi session.
1. Open the manager
/sf-piUse the manager to list bundled extensions, enable or disable optional surfaces, open configuration panels, inspect recommendations, and run doctor checks.
2. Check Salesforce context
/sf-orgThis shows the Salesforce CLI target org information that SF Pi will use for org-aware workflows. If no org is connected, authenticate with the Salesforce CLI outside pi, then reload the session.
3. Inspect the dev status surfaces
/sf-devbar
/sf-lsp/sf-devbar explains the status bar and footer state. /sf-lsp shows advisory Apex, LWC, and Agent Script diagnostic status.
4. Try the Salesforce-aware tools
Choose the surface that matches your task:
| Task | Start here |
|---|---|
Build or test .agent files | /sf-agentscript |
| Work with Data Cloud / Data 360 | /sf-data360 |
| Use Salesforce UI as a last-mile fallback | /sf-browser |
| Search Slack from pi | /sf-slack |
| Explore Salesforce data read-only | /sf-data-explorer |
| Review safety gates | /sf-guardrail |
| Manage Salesforce skills | /sf-skills |
5. Start a focused non-MCP session
Pi 1.2.0 accepts * patterns in --tools, so a session can expose only the Salesforce family needed for the current task. These profiles use Pi's native tool selection and do not create SF Pi settings or a second exposure model. Quote each pattern so the shell does not expand it.
# Salesforce Browser
pi --no-mcp --tools read,bash,edit,write,'sf_browser_*'
# Agent Script
pi --no-mcp --tools read,bash,edit,write,'agentscript_*'
# Data 360
pi --no-mcp --tools read,bash,edit,write,sf_data360--no-mcp makes these examples fully independent of configured MCP servers. Remove it when the task requires MCP. --tools by itself keeps MCP tools available unless the selection explicitly filters MCP names.
Pi 1.2.0 also accepts exact-name modifiers such as pi --tools +codemode,-write for one-run adjustments to the default tool set. Modifiers do not accept * patterns, so the focused family profiles above remain explicit allowlists.
6. Use generated references
- Bundled Extensions shows every extension and runtime surface.
- Command Reference lists every slash command.
- Troubleshooting points to common recovery paths.
Recommended first session
/sf-pi status
/sf-org
/sf-devbar
/sf-guardrail
/sf-pi recommendedThen pick the extension that matches the work in front of you.