Report an issue
Bugs & feature requests
File these on GitHub Issues . Add the relevant area label so it routes correctly:
| Label | Use for |
|---|---|
area: cli | The @sfdt/cli command-line tool |
area: extension | The Chrome extension |
area: vscode | The VS Code extension |
area: host | The native-messaging host |
A good bug report includes
Versions
sfdt version
node --version
sf --versionFor the Chrome extension, note the version shown on chrome://extensions; for VS Code, the
extension version in the Extensions panel.
What you ran and what happened
The exact command or feature, the full output (redact secrets), and what you expected instead.
Diagnostics
sfdt doctor --extension --jsonAttach the output for bridge/extension issues.
A minimal repro
The smallest project state or steps that reproduce it.
Security vulnerabilities
Do not open a public issue for a security vulnerability. Use the private channel below so it can be fixed before disclosure.
Report security issues through
GitHub’s private security advisory flow .
See SECURITY.md for the full
policy. See also Security & privacy.
Contributing a fix
Pull requests are welcome. The short version:
git checkout -b feature/your-feature
# make changes with tests
npm test && npm run lint
git commit -m "feat: ..."Open a PR against main. See
CONTRIBUTING.md.