Mbbrowser Help

English

简体中文
한국어
Русский
日本語
Português
Tiếng Việt
繁體中文
Français

English

简体中文
한국어
Русский
日本語
Português
Tiếng Việt
繁體中文
Français

Appearance

MBAgent FAQ ​

This article aggregates common MBAgent usage problems and solutions. If your problem is not in this article, please contact Mbbrowser customer support.

1. Installation and Launch ​

Q1.1: Double-clicking the MBAgent icon does nothing ​

Possible causes:

  • Mbbrowser not started
  • Mbbrowser account not logged in
  • Insufficient working directory permissions

Solution:

  1. Start Mbbrowser and log in
  2. Check if MBAgent working directory exists
  3. Launch MBAgent with administrator privileges

Q1.2: "Select Working Directory" stays after launch ​

Cause: Mbbrowser main program is not started; MBAgent cannot read Mbbrowser account info.

Solution:

  1. Close MBAgent
  2. Start Mbbrowser and log in
  3. Restart MBAgent

Q1.3: Chinese displays as garbled after launch ​

Solution:

  1. Windows Settings → Time & Language → Language → Windows display language → Simplified Chinese (China)
  2. Restart computer

Q1.4: Installer says "A newer version is already installed" ​

Solution:

  1. Control Panel → Programs and Features → Uninstall old Mbbrowser
  2. Delete C:\Program Files\Mbbrowser
  3. Reinstall new version

2. Connecting Mbbrowser ​

Q2.1: MBAgent shows "Waiting for Mbbrowser CDP" ​

Possible causes:

  • Mbbrowser not started
  • ControlV2 port occupied
  • Firewall blocking

Solution:

  1. Start Mbbrowser
  2. Check Mbbrowser → Settings → whether ControlV2 is enabled
  3. Close firewall / antivirus

Q2.2: AI can't operate Mbbrowser ​

Troubleshoot steps:

  1. Go to "Settings → Official Service Detection"
  2. Click "Start Detection" under "Mbbrowser Client ControlV2"
  3. View the specific failed step

Q2.3: AI operations on Mbbrowser always fail ​

Possible causes:

  • Mbbrowser account quota exhausted
  • Mbbrowser environment corrupted
  • Network issue

Solution:

  1. Check Mbbrowser account AI quota
  2. Manually test the environment inside Mbbrowser
  3. Contact Mbbrowser customer support

Q2.4: Can a remote Mbbrowser be controlled? ​

✅ Yes, but you need:

  1. Remote machine starts Mbbrowser
  2. Expose ControlV2 port
  3. Configure remote IP + port inside MBAgent

⚠️ Use only on trusted networks (VPN / intranet).

3. Models and Provider ​

Q3.1: Model list is empty ​

Cause: Mbbrowser account has not enabled AI model quota.

Solution:

  1. Visit Mbbrowser console
  2. Go to "AI Models" → enable quota
  3. Return to MBAgent → refresh model list

Q3.2: List doesn't change after switching Provider ​

Troubleshoot:

  1. Check if that Provider has API Key configured
  2. Test if connection succeeded
  3. Restart MBAgent

Q3.3: Custom Provider can't connect ​

Troubleshoot:

  1. Check if API Key and Base URL are correct
  2. Test network connectivity (ping / curl)
  3. Check MBAgent logs (%LOCALAPPDATA%\mbagent\logs\)

Q3.4: Model responds very slowly ​

Possible causes:

  • Network issue
  • Model overloaded
  • Context too long

Solution:

  1. Switch to a faster model
  2. Compress session history (/compact)
  3. Check network

4. Tasks and Scheduling ​

Q4.1: Scheduled task didn't trigger as expected ​

Troubleshoot:

  1. Check cron expression
  2. Check if MBAgent is running (Daemon not installed)
  3. View task history
  4. Confirm system time

Q4.2: Tasks don't execute when computer sleeps ​

Solution:

  1. Install MBAgent Daemon
  2. Set computer not to sleep
  3. Configure wake timers

Q4.3: Tasks keep failing ​

Troubleshoot:

  1. Run task alone to see error
  2. Check Mbbrowser browser online status
  3. Simplify task description, troubleshoot step by step
  4. Contact Mbbrowser customer support

Q4.4: Scheduled task consumes too many Tokens ​

Solution:

  1. Use cheap model
  2. Close "show thinking process"
  3. Reduce execution frequency
  4. Optimize prompt

5. Files and Attachments ​

Q5.1: Large file upload failed ​

Limit:

  • Single file recommended < 50 MB
  • For super large files (>100 MB), use AI tool to read path

Solution:

  1. Compress file (zip)
  2. Use Read tool to let AI read it itself
  3. Upload in chunks

Q5.2: AI can't see the image ​

Possible causes:

  • Current model doesn't support multimodal
  • Image too large
  • Image format not supported

Solution:

  1. Switch to a multimodal-capable model (gpt-5, claude-sonnet-4)
  2. Compress the image
  3. Convert to JPG / PNG

Q5.3: Files modified by AI are not saved ​

Troubleshoot:

  1. Did you accidentally click "Reject"?
  2. Does the working directory have write permission?
  3. Check whether the AI memory bank recorded wrong paths

6. Permission and Security ​

Q6.1: How to revoke AI's incorrect operation? ​

Steps:

  1. Immediately press Esc to stop AI
  2. View operation log
  3. Manually revoke AI's incorrect operation

Q6.2: AI deleted my files, how to recover? ​

Case 1: File is inside sandbox (working directory)

  • If "backup" was enabled, recover from backup
  • Otherwise need professional recovery tools

Case 2: File is outside sandbox (system directory)

  • ⚠️ Such operations are blocked by default
  • If it happened, please contact Mbbrowser customer support immediately

Prevention:

  • Let AI back up important files before operating them
  • Use Ask mode (popup confirmation)

Q6.3: Is API Key safe? ​

✅ Safe:

  • MBAgent won't upload API Key
  • Key is only stored in Windows Credential Manager
  • Credentials are cleared when MBAgent is uninstalled

⚠️ Recommendations:

  • Regularly rotate API Key
  • Don't paste plaintext Key in memory bank or sessions

7. AI Memory Bank ​

Q7.1: AI seems not to "remember" what I said before ​

Troubleshoot:

  1. Check if the memory exists in AI memory bank
  2. Re-ask AI to remember and confirm
  3. Check if the working directory changed

Q7.2: AI used wrong memory ​

Solution:

  1. Edit that memory
  2. Correct or delete

Q7.3: How to back up memory bank? ​

  1. Find directory: %LOCALAPPDATA%\mbagent\memory\
  2. Copy entire folder
  3. Store in a safe place

8. Interface and Display ​

Q8.1: Interface lag ​

Possible causes:

  • Insufficient system resources
  • Too many sessions / KMS / MCP loaded
  • Theme rendering issue

Solution:

  1. Close unneeded tabs
  2. Reduce session count
  3. Switch theme (dark < light)
  4. Restart MBAgent

Q8.2: Font display abnormal ​

Solution:

  1. Check if system fonts are complete
  2. Switch font in MBAgent settings

Q8.3: Tab bar not visible ​

Solution:

  1. Settings → Interface & Navigation → Show which tabs → check all
  2. Restart MBAgent

9. Performance Optimization ​

Q9.1: MBAgent high memory usage ​

Normal range:

  • Idle: 200-500 MB
  • Complex task: 1-2 GB
  • High concurrency: 2-4 GB

Optimization:

  1. Close unneeded sessions
  2. Reduce concurrent task count
  3. Uninstall unused MCP services

Q9.2: AI replies slowly ​

Possible causes:

  • Model server latency
  • Network issue
  • Context too long

Optimization:

  1. Switch to a faster model
  2. Compress history
  3. Check network

10. Update and Upgrade ​

Q10.1: How to update MBAgent? ​

MBAgent updates with Mbbrowser:

  1. Mbbrowser auto-detects new version on launch
  2. Update prompt pops up
  3. Click "Update Now"
  4. Restart after update

Q10.2: Data lost after update? ​

Won't:

  • AI memory bank, sessions, KMS all preserved
  • Only config files may be reset

If data is lost:

  1. Check backup directory
  2. Recover from backup
  3. Contact Mbbrowser customer support

Q10.3: Can you roll back to an older version? ​

Yes, but you need:

  1. Back up current data
  2. Uninstall current version
  3. Install old version
  4. Restore data

⚠️ Note: Old versions may not support new features.

11. Error Codes ​

BROWSER_AUTO_UNAVAILABLE ​

Meaning: Browser automation capability unavailable. Cause: Playwright MCP browser not started. Solution:

  1. Install Node.js and npx
  2. Let MBAgent auto-install Playwright
  3. Restart MBAgent

CONTROL_V2_DISCOVERING ​

Meaning: Discovering Mbbrowser client instances. Cause: Just started or scanning. Solution: Wait a few seconds and retry.

CONTROL_V2_HANDSHAKE_SPEC_MISMATCH ​

Meaning: MBAgent and Mbbrowser client use different ControlV2 spec versions. Solution:

  1. Update Mbbrowser to the latest version
  2. Update MBAgent to the latest version

TOOL_ENABLE_PREREQUISITE_MISSING ​

Meaning: Tool's prerequisites not met. Solution:

  1. Check if the corresponding Skill is enabled
  2. Check Mbbrowser account authorization level

Mbbrowser RAG Knowledge Base Currently Unavailable ​

Meaning: Mbbrowser official RAG knowledge base service abnormal. Solution:

  1. Check if Mbbrowser account is valid
  2. Check network
  3. Contact Mbbrowser customer support

Mbbrowser Client ControlV2 Currently Unavailable ​

Meaning: Mbbrowser browser ControlV2 protocol abnormal. Solution:

  1. Restart Mbbrowser browser
  2. Restart MBAgent
  3. Check Mbbrowser browser → Settings → ControlV2

12. Getting Help ​

Official Channels ​

Self Troubleshooting ​

  1. Check MBAgent log: %LOCALAPPDATA%\mbagent\logs\
  2. Check Mbbrowser browser log
  3. Use "Settings → Official Service Detection" to check service status

Feedback ​

When contacting customer support, please provide:

  • MBAgent version number
  • Mbbrowser browser version number
  • Windows version
  • Complete error message
  • Operation steps
  • Provide log files when necessary

Back: MBAgent intro or Download & Install MBAgent.