Resetting Bob to resolve persistent issues

Various error messages or unexpected behavior that persists despite attempting other fixes.

• Residual configuration conflicts: Settings or cached data from the previous version may conflict with the updated application
• Name change transition issues: The transition from the old name to Bob may have left incompatible data
• Corrupted local state: Application state may have become corrupted during the update process

Resetting Bob clears all local application data and settings, resolving most persistent issues related to the name change transition. This is a last resort solution when other troubleshooting steps have failed.

• Export your settings to save your current IDE settings and preferences.

1. Click the settings cog icon in the Bob panel
2. Click the Export button, next to Export Bob settings to a JSON file
3. Select a location to save the file

• Consider saving any custom instructions or rules you have created.

1. Open IBM Bob
2. Click the settings cog icon in the Bob panel
3. Click the Reset button to reset all state and secret storage.
4. Confirm the reset when prompted
5. Restart IBM Bob
6. Open IBM Bob and log back into your account

After logging back in, you will need to reconfigure:

• Custom instructions
• Mode preferences
• Any workspace-specific settings
• MCP server connections