type_text and evaluate_javascript incorrectly return "Browser automation requires a paid Donut Browser plan"

[VladimirBigunenko]

Title: type_text and evaluate_javascript incorrectly return "Browser automation requires a paid Donut Browser plan"

Description:
Even with an active Pro (Monthly) subscription (1/20 profiles used), the type_text and evaluate_javascript MCP tools return:

{"code":-32000,"message":"CDP error: {\"code\":-32000,\"message\":\"Browser automation requires a paid Donut Browser plan.\"}"}

This is incorrect according to the official documentation.

Evidence that this is a bug:

1. Documentation states automation is FREE:
From https://context7.com/zhom/donutbrowser:

"Browser automation does NOT require a paid plan. All automation features are included with Donut Browser at no additional cost."
"Local REST API - Available by default, No payment required"
"MCP (Model Context Protocol) - Supported for AI integrations, Free to use"

2. CDP port is active and responds:

$ curl http://127.0.0.1:45507/json/version
{
  "Browser": "Chrome/146.0.7680.164",
  "Protocol-Version": "1.3",
  ...
}

3. navigate works fine (also uses CDP):

$ curl -X POST http://127.0.0.1:51080/mcp/TOKEN \
  -d '{"method":"tools/call","params":{"name":"navigate","arguments":{"profile_id":"c8e3b723-...","url":"https://onlyfans.com"}}}'
{"result":{"content":[{"text":"Navigated to https://onlyfans.com/..."}]}}  ✅ SUCCESS

4. But type_text fails with false error:

$ curl -X POST http://127.0.0.1:51080/mcp/TOKEN \
  -d '{"method":"tools/call","params":{"name":"type_text","arguments":{"profile_id":"c8e3b723-...","selector":"div[contenteditable=true]","text":"Hello"}}}'
{"error":{"code":-32000,"message":"CDP error: {\"code\":-32000,\"message\":\"Browser automation requires a paid Donut Browser plan.\"}"}}

5. Tested on BRAND NEW profile (no cookies, no extensions):

• Profile: TestAutomationFix (ID: c8e3b723-1d93-4f49-bb65-d899167b20d4)
• Created fresh during testing
• Error still occurs on new profile

6. Playwright direct CDP connection fails too:

const browser = await chromium.connectOverCDP('http://127.0.0.1:45507');
// page.type() and page.fill() also fail with same error

Environment:

• Donut Browser: v0.22.5
• Browser engine: Wayfern 146.0.7680.166
• OS: Linux x86_64 (CachyOS/Arch)
• Subscription: Pro (Monthly) - 1/20 profiles
• MCP Server: Running on port 51080
• CDP Port (tested): 45507

Steps to reproduce:

1. Launch any Wayfern profile via MCP
2. Call type_text or evaluate_javascript tool
3. Receive error: "Browser automation requires a paid Donut Browser plan."

Expected behavior:

According to documentation, automation tools should work without requiring a paid plan. The error message is misleading - it suggests a missing subscription, but the user already has Pro plan active.

Additional info:

• Log shows: "Browser automation requires a paid Donut Browser plan." even with Pro subscription
• Navigation works (which also uses CDP protocol)
• The error comes from the browser engine itself via CDP
• Possibly related to: cookie decryption errors seen in logs:

  [ERROR] Pre-launch: Cookie decryption FAILED for '__AP_SESSION__'
  

Suggested fix:

Review the CDP command filtering logic - it appears to incorrectly block automation commands even when the user has valid Pro subscription (or even according to docs, when it should be free for all).

---

Link to documentation: https://context7.com/zhom/donutbrowser
Test repo: https://github.com/zhom/donutbrowser

[github-actions]

Thanks for opening your first issue!

This is a well-documented bug report with clear reproduction steps and environment details.

Missing information:

1. Could you share the relevant app logs from ~/.local/share/DonutBrowser/logs/? Specifically, any log lines around the time you call type_text or evaluate_javascript — this will help confirm whether the subscription check (has_active_paid_subscription) is returning false despite your active Pro plan, or if the error originates from somewhere else.

   cat ~/.local/share/DonutBrowser/logs/*.log | grep -i -A5 "subscription\|paid\|automation" | tail -50

2. When you say navigate works — does it consistently work every time, or did it perhaps work before the subscription check was added? (This would help narrow down whether it's a caching/timing issue with subscription validation.)

3. Are you logged into your Donut Browser account in the app's settings/account section, and does it show your Pro subscription as active there?

[VladimirBigunenko]

@github-actions Thank you for the quick response! Here are the answers to your questions:

1. App logs around type_text / evaluate_javascript calls:

From ~/.local/share/DonutBrowser/logs/ (excerpt during type_text call):

[2026-05-02 12:24:40.793][donutbrowser_lib::wayfern_manager][INFO] CDP ready on port 45363 after 2 attempts
[2026-05-02 12:24:40.885][donutbrowser_lib::wayfern_manager][INFO] Successfully applied fingerprint to page target: Object {}
[2026-05-02 12:24:40.901][donutbrowser_lib::browser_runner][INFO] Wayfern launched successfully with PID: 282486

When calling type_text via MCP:

$ curl -X POST http://127.0.0.1:51080/mcp/TOKEN \
  -d '{"method":"tools/call","params":{"name":"type_text","arguments":{"profile_id":"...","selector":"div[contenteditable=true]","text":"Hello"}}}'
{"error":{"code":-32000,"message":"CDP error: {\"code\":-32000,\"message\":\"Browser automation requires a paid Donut Browser plan.\"}"}}

The error comes from the browser engine itself via CDP, not from the MCP server.

2. Does navigate work consistently?

✅ Yes, navigate works consistently EVERY time:

$ curl -X POST http://127.0.0.1:51080/mcp/TOKEN \
  -d '{"method":"tools/call","params":{"name":"navigate","arguments":{"profile_id":"c8e3b723-...","url":"https://onlyfans.com"}}}'
{"result":{"content":[{"text":"Navigated to https://onlyfans.com/...","type":"text"}]}}  ✅ SUCCESS

This is strange because:

• navigate uses CDP protocol → works
• type_text uses CDP protocol → blocked with "paid plan" error
• Both use the same underlying CDP connection

3. Donut Browser account status:

✅ Yes, logged in and Pro subscription is active:

From the app logs:

[2026-05-02 12:09:32.621][donutbrowser_lib::sync::subscription][INFO] Connected to sync subscription at https://sync.donutbrowser.com/v1/objects/subscribe
[2026-05-02 12:09:33.445][donutbrowser_lib::cloud_auth][INFO] Wayfern token acquired

From the app GUI:

• Email:
• Тариф: Pro (Monthly)
• Профили: 1 / 20

Additional evidence this is a bug:

Documentation states automation is FREE:

From https://context7.com/zhom/donutbrowser:
"Browser automation does NOT require a paid plan. All automation features are included with Donut Browser at no additional cost."
"Local REST API - Available by default, No payment required"

Tested on BRAND NEW profile:

• Created profile: TestAutomationFix (ID: c8e3b723-1d93-4f49-bb65-d899167b20d4)
• No cookies, no extensions, fresh profile
• Error still occurs: "Browser automation requires a paid Donut Browser plan."

CDP port responds to basic queries:

$ curl http://127.0.0.1:45507/json/version
{
  "Browser": "Chrome/146.0.7680.164",
  "Protocol-Version": "1.3",
  ...
}

Summary:

• navigate (CDP) → ✅ Works
• type_text (CDP) → ❌ Blocked with false error
• evaluate_javascript (CDP) → ❌ Blocked with false error
• Pro (Monthly) active → ✅ Confirmed
• Documentation says automation is free → ✅ Confirmed

**The subscription check logic (has_active_paid_subscription) appears to be incorrectly blocking automation commands even when:

1. User has active Pro subscription
2. Documentation states automation is free for all users
3. Commands are sent to a valid, running profile

Would you like me to enable debug logging and capture the exact subscription check response?

[zhom]

Hi there and thank you for the report! Thank you for purchasing Pro as well.

The website you linked is not the official documentation, it is an AI generated summary I have no relation to. I understand the confusion as there is over a dozen of websites that generate some form of documentation for the project without mentioning that they are not associated with it or that the docs are AI generated. The official sources of truth is the GitHub repo and https://donutbrowser.com.

I've quickly checked the issue and it seems to be a Cloudflare problem, which blocks requests to the endpoint generating the paid token. I disabled as much as possible for the token generation endpoints. Can you please restart the app and let me know if you are still unable to use browser automation?

[VladimirBigunenko]

Hi @zhom, thank you for the fix!

Unfortunately, I'm still seeing the same error after fully restarting the application and using a fresh token.

Test results:

• **** $\rightarrow$ ✅ Works consistently.
• **** $\rightarrow$ ❌ Still returns:
• **** $\rightarrow$ ❌ Same error.

I tested this on both my main profile and a brand new clean profile. My subscription is definitely Pro (Monthly).

It seems that while navigation is allowed, any interactive CDP commands are still being blocked by the subscription check logic. Could you please take another look?

[VladimirBigunenko]

Hi @zhom, the issue persists in v0.24.0. I have done deeper investigation and have new findings.

The Cloudflare fix did not help — the Wayfern token IS being acquired and passed correctly:

[2026-05-12 12:13:17.390][donutbrowser_lib::cloud_auth][INFO] Wayfern token acquired

chrome --wayfern-token=3ca8850c5d41fea297f119fc0bcf85d9539fe2e1bb4b632d727c594645c59096 ...

Subscription confirmed active via cloud_auth_state.json:

{
  "user": {
    "plan": "pro",
    "planPeriod": "monthly",
    "subscriptionStatus": "active"
  }
}

Key new finding — this is a Wayfern binary issue, not an MCP/token issue:

Wayfern.setFingerprint ✅ works
Page.navigate ✅ works
Page.captureSnapshot ✅ works
Network.getCookies ✅ works
Runtime.evaluate ❌ blocked: "Browser automation requires a paid Donut Browser plan"
Input.dispatchKeyEvent ❌ blocked: same error
Page.addScriptToEvaluateOnNewDocument ❌ blocked: same error

The Wayfern binary (closed source) is filtering CDP commands internally — it allows passive commands (navigate, getCookies, captureSnapshot) but blocks interactive ones (evaluate, input, script injection). The --wayfern-token flag is present but Wayferns server-side validation still returns "free plan" for automation features.

Could you check whether the Wayfern CDP command filtering is server-side and whether our specific token (3ca8850c...) has automation permissions enabled on the Wayfern backend? The fingerprint API works so the token IS valid, but interactive CDP commands are still being rejected.

Thanks!

[VladimirBigunenko]

Update after re-login and v0.24.0 testing:

I logged out and logged back in. The subscription is confirmed active:

{"plan":"pro","subscriptionStatus":"active"}

But the Wayfern token is still not being generated. After re-login:

• cloud_auth_state.json shows correct Pro plan
• No "Wayfern token acquired" in logs
• Chrome launches without --wayfern-token flag
• The error persists: "Browser automation requires a paid Donut Browser plan."

This confirms the issue is that api.donutbrowser.com is not returning a Wayfern token for Pro accounts. The token generation endpoint appears to be blocked by Cloudflare as you mentioned. Even after re-authentication, the token is never issued.

Could you check on your end whether the token endpoint is functioning? The API root responds (HTTP 401), but the Wayfern token endpoint specifically does not return tokens for our account.

curl https://api.donutbrowser.com/api/auth/wayfern-start → no token returned

[zhom]

Hi there :) Is the issue still present? I reached out to you via your email. If you prefer, we can communicate via DMs for faster info exchange. Thanks!

[zhom]

Closing this due to inactivity. If you believe the issue is not resolved, please re-open it and provide an update. Thanks!