Debug Logging

Debug logging captures detailed records of Agentforce Vibes activity to help you troubleshoot issues. Logging is off by default. Enable it when you must investigate unexpected behavior or prepare a bug report.

  1. Open the Agentforce Vibes panel and click the Settings icon (⚙) in the top-right corner.
  2. Click Logging to expand the section.
  3. Toggle debug logging on.

Agentforce Vibes starts writing detailed logs to disk immediately. The toggle shows the current state—on or off.

Two log files are available under LOG FILES:

FileDescriptionMax Size
Open activity logTimeline of extension events. Start here for most bug reports.10 MB
Open full traceFull request and response detail for each model call.50 MB

Click either to open it in your editor. If a file shows 0 KB, Agentforce Vibes hasn’t written any log data yet in the current session.

Use the activity log for general troubleshooting. Use the full trace when you must inspect exactly what the agent sent to and received from the model.

Three options under Advanced control log behavior:

Auto-off After 24 hours—Agentforce Vibes automatically turns off debug logging After 24 hours. The toggle shows the scheduled off time (for example, “Turns off Jun 2, 4:42 PM”). Enable this option to avoid accumulating large log files during normal development.

Wipe logs on reload—clears both log files when VS Code reloads the window. Enable this option to start each session with a clean log. Disable it when you want logs to persist across reloads for extended troubleshooting.

Redact sensitive data—scrubs home path, tokens, and email addresses from log files before writing them to disk. This option is off by default so that raw developer logs include full context. Enable it before sharing logs with your team.

  • Debug logging is off by default. Agentforce Vibes doesn’t write log files until you enable it.
  • The activity log and full trace are independent files. You can open either one while logging is active.
  • Agentforce Vibes stores log files locally on your machine and doesn’t send them to Salesforce.
  • Enable Redact sensitive data before attaching logs to bug reports or sharing with support.