SF Browser
Salesforce-aware browser automation for last-mile UI work using agent-browser.
What it does
Salesforce-aware agent-browser affordance layer for UI last-mile work that Salesforce APIs cannot cover. It registers a cache-first /sf-browser panel plus a small hot-path browser tool set, curated Setup Destinations, Browser Evidence, and lazy agent-browser invocation after explicit command/tool intent.
Start
Open the extension from its primary command:
text
/sf-browserOpen its Manager detail or change its package state with:
text
/sf-pi open sf-browser
/sf-pi enable sf-browser
/sf-pi disable sf-browserSafety notes
- No startup probes; agent-browser is detected only from /sf-browser doctor or explicit tool/command actions.
- Browser Evidence is artifact-first and stored outside the project by default.
- Snapshots publish compact ref metadata so SF Guardrail can classify committing click refs from the latest accessible label.
- Session-bearing Salesforce org-open URLs are passed to agent-browser but not echoed in tool results.
Exact reference
Show commands, tools, providers, and hooks
- Extension id:
sf-browser - Intent: Work with Salesforce orgs
- Category: Agent Tool
- Maturity: experimental
- Default state: on
- Commands:
/sf-browser - LLM tools:
sf_browser_open_org,sf_browser_snapshot,sf_browser_click,sf_browser_fill,sf_browser_select,sf_browser_press,sf_browser_editor,sf_browser_wait,sf_browser_capture_evidence,sf_browser_resolve_path - Providers: none
- Events/hooks:
session_start,session_shutdown
For contributors
Troubleshooting
See the Troubleshooting section in the full README for extension-specific recovery steps.