openclaw - 💡(How to fix) Fix Browser Relay: multi-profile switcher for multiple OpenClaw instances [3 comments, 3 participants]

Use case: Users running multiple OpenClaw instances (e.g. home server + VPS, or two AI companions) have to manually re-enter gateway credentials every time they switch — friction-heavy and error-prone.

Fix Plan

To implement named profile slots in the extension options page, follow these steps:

• Update the options.html file to include a profile selection dropdown and a "Set as Active" button.
• Modify the options.js file to store and retrieve profile data from storage.
• Update the background.js file to read the active profile's connection settings and reconnect automatically when the active profile is changed.

Example Code

// options.js
// Store profile data in storage
function saveProfile(profile) {
  chrome.storage.local.set({ profiles: profile });
}

// Retrieve profile data from storage
function getProfiles() {
  return chrome.storage.local.get('profiles');
}

// background.js
// Read active profile's connection settings
function getActiveProfile() {
  return chrome.storage.local.get('activeProfile');
}

// Reconnect automatically when active profile is changed
chrome.storage.onChanged.addListener(function(changes, area) {
  if (area === 'local' && changes.activeProfile) {
    reconnectRelay();
  }
});

// reconnectRelay function remains the same as before

Verification

To verify that the fix worked, follow these steps:

• Open the extension options page and create a new profile.
• Switch to a different profile and verify that the connection settings are updated.
• Verify that the background service worker reconnects automatically when the active profile is changed.

Extra Tips

• Make sure to handle errors and edge cases when storing and retrieving profile data.
• Consider adding a "Delete Profile" button to remove unused profiles.
• Test the implementation thoroughly to ensure backward compatibility with existing users.