Troubleshooting
Start with the symptom closest to what you see. For extension-specific fixes, use the generated index on this page.
SF Pi does not load
Restart pi or run
/reload.Confirm the package is installed in the expected scope:
text/sf-pi statusVerify Node.js is at least
22.19:bashnode --versionReinstall the package if pi cannot find it:
bashpi install git:github.com/salesforce/sf-pi
Salesforce commands cannot find an org
SF Pi uses Salesforce CLI authentication. Check the CLI directly:
sf org list --all
sf config get target-orgAuthenticate or set the target org with the Salesforce CLI, then reload pi.
Glyphs render as question marks
Run the font helper and switch your terminal to the installed Nerd Font:
/sf-setup-fontsA bundled extension is noisy or not needed
Use the manager to disable optional extensions globally or for the current project:
/sf-pi
/sf-pi disable <extension-id>
/sf-pi enable <extension-id>Always-on manager behavior is mediated by SF Pi Manager and cannot be disabled from inside the package.
Slack tools are unavailable
Slack tools register only after an auth token is available. Run:
/sf-slackThen follow the setup panel. If auth is missing, use /login sf-slack or your approved automation token path.
Data 360 or Agent Script calls fail
Confirm that the target Salesforce org is connected and has the required features enabled. Start with the extension panels:
/sf-data360
/sf-agentscriptFor Data 360 readiness, use the read-only probe surface from /sf-data360.
Extension troubleshooting index
Jump to an extension's Troubleshooting section to see the full fix. This index is generated from the ## Troubleshooting section in each extension README, so it never drifts.
- The Manager cannot find SF Pi in settings
- A toggle does not take effect
- A newer stable Pi version is outside the audited window
- Auto Update skipped a package
- Auto Update waits for
agent_settled - Project changes do not stick
- Recommended items or skill roots look stale
pi-web-accessreportsBlocked internal addressfor a public site
- No models are available after installation
- Login saved the credential but refresh failed
- Refresh reports no assigned models
- A request reports
team_model_access_denied - A request says the provider is not configured
- A discovered model shows conservative metadata
- Requests fail while
curlworks on macOS - Usage or throttle status is stale
- Thinking changes after a model switch
- Saved and environment credentials conflict
- The dedicated compaction model falls back to the active model
- Agent Script SDK is unavailable
- Server compile rejects locally valid syntax
- A preview session is missing
- An eval appears stuck
- Live trace fetch returns no data
- Publish or activation fails on the agent user
sf_apexcannot resolve the org- No log appears during
log.watch - Anonymous Apex is refused as mutating
agent-browseris missing- Chrome cannot launch in a container
- A snapshot ref fails
- Screenshots are too heavy
- The action is outside the hot path
- The doctor says the plugin is missing
- PMD, CPD, or SFGE rules fail
- Flow Scanner rules fail
- A scan wrote unexpected files
- A DMO list returns too much data
- Metadata search fails while DMO/DLO lists work
- A connector detail returns
NOT_FOUND - The family tools are missing
- A mutation is blocked headlessly
- A versioned path is rejected
- SF Docs is not configured
- Collections look stale
- Fetch returns the wrong locale or version
sf_herdr_planis unavailable- An ephemeral pane stayed open
- The Herdr package is missing
- Startup errors about
herdr_layout/herdr_pane/herdr_agentconflicts
- No
sfdx-project.jsonis found - No components are found
- The local Jest runner is missing
- Jest fails without JSON
- Apex or schema validation is needed
- No Slack status or tools appear
- Status says connected but limited
- Status reports a bot or unsupported token
- Opening a DM says
im:writeis missing - A fuzzy person/channel resolves incorrectly
- Canvas read cannot find content
- Scheduled delivery is absent from the Slack client Scheduled tab
- A run returns a safety review
- Salesforce reports
INVALID_TYPE - Salesforce reports
INVALID_FIELD - No query plan is available
- The full result is absent from chat
- Export rejects a path
- No tldraw document is open
- Runtime configuration is stale
- The app-owned skill is missing or stale
- A document reached its page limit
- Readiness blocks completion
- Production confirms fire for a sandbox
- A protected file remains blocked after removing an override
- Headless CI is blocked
- Audit is empty after resume
- The constitution never appears in model context
- User guidance does not take effect
- An Instruction Surface baseline is not comparable
- The flow opens a browser instead of creating an issue
- The account cannot create public issues
- Diagnostics contain
unknownorunavailable - A private value appears in preview
- The Welcome row stays unknown
- Transcript rows are too chatty or quiet
- Setup guidance appears once and then stops
- Apex diagnostics never appear
- LWC diagnostics never appear
- The first-boot prompt did not appear
- Installation appears slow
.agentdiagnostics are absent
- The transport cannot be initialized
- Catalog loading does not finish
- A query is refused
- Exports are not where expected
- The bars do not appear
- The org segment stays pending
- Context says
unknown - The gateway badge color is unexpected
- An
img:Ncpill appears
- No spinner appears
- The message looks truncated
- Skills appear duplicated
- A project skill is locked
- A conflict is report-only
- A custom source vanished
- The funnel is slow to open
- Toggles vanished after update
- A skill-readiness warning appears
- Glyphs render as boxes
- The LSP row stays unknown
- Herdr reports missing tools
- Herdr tool-name conflicts at startup
- Startup feels noisy
- Content is clipped
- Fonts are installed but glyphs remain wrong
More troubleshooting links
- Command reference: Commands
- Extension inventory: Bundled Extensions
- File an issue: github.com/salesforce/sf-pi/issues