Tutorial August 24, 2026

Perplexity Comet With Clash Verge: Access Setup Guide 2026

Trying Perplexity Comet but seeing sign-in errors, blank pages, or slow AI responses? Follow this beginner-friendly Clash Verge walkthrough to import a subscription, choose a suitable server, configure split tunneling, and build a more reliable environment for Comet.

Docker Proxy GitHub Acceleration Advanced Config YAML

1. What this setup solves—and what it cannot

You are trying Perplexity Comet, but the browser does not behave like an ordinary web page. A sign-in loop, a blank workspace, or an AI answer that stops after the first few tokens can come from several different layers: account eligibility, browser storage, DNS resolution, a congested relay, or a desktop proxy setting that Comet never inherited. This guide focuses on the networking and client side of that problem. It shows how to use Clash Verge to import a subscription, select a responsive server, and route Comet-related traffic without automatically sending every application on your computer through the same tunnel.

The goal is not to promise access to a feature that your account or region does not support. A proxy cannot create a Perplexity account, remove a billing requirement, or repair a provider-side outage. It can, however, make the connection path more predictable when ordinary browser traffic is being interrupted by packet loss, unreliable DNS, restrictive filtering, or a route with poor international peering. You should also confirm that using a third-party proxy is allowed by your employer, school, or local network policy. Prompts may contain sensitive research, customer information, or source material, so treat every relay as untrusted infrastructure.

In 2026, Comet may involve more than one visible tab. The browser shell can load static JavaScript from a content delivery network, authenticate through account services, open persistent connections for answer streaming, retrieve citations from search infrastructure, and download images or documents from separate hosts. A single “VPN on” switch hides these differences. Clash Verge gives you a way to observe the traffic and decide which domains should use a stable proxy group while local services, work resources, and ordinary domestic websites remain on DIRECT.

A successful test is not merely “the page opened once.” It is a repeatable sign-in, a complete Comet interface, and several streamed answers that remain responsive after the browser has been running for a while.

2. Prepare Clash Verge before opening Comet

Start with a current Clash Verge build that uses the Mihomo core, then open the application and verify that the core is actually running. Client interfaces differ slightly between releases, but the workflow is usually the same: add a profile, update it, select it as active, and choose a proxy mode. Do not begin troubleshooting from a browser tab that has been open for hours. Old cookies, cached failed redirects, and stale DNS answers can make a corrected network path look broken.

Import and validate a subscription

Open the Profiles or Subscriptions section and paste the subscription URL supplied by your provider. Give the profile a recognizable name, such as AI-work-profile, instead of leaving it as a random URL. Click the update button and wait for Clash Verge to parse the YAML. If the update fails, inspect the error before changing Comet settings: an expired URL, an HTML login page returned instead of YAML, a certificate error, or a provider quota limit must be fixed at the subscription level.

After the profile loads, inspect the proxy groups. Prefer a group that supports manual selection or latency testing rather than a group locked to an opaque automatic rule. Test several nearby exits and record both latency and stability. A server showing 80 milliseconds in a one-time test may still be a poor choice if it loses packets during a long response stream. For Comet, sustained reliability is generally more important than the lowest initial ping because the browser may maintain multiple connections while an answer is being generated.

Choose the least invasive operating mode

Begin with Rule mode. It lets explicit domain rules select the proxy while unmatched traffic follows your profile’s final policy. Global mode is useful as a short diagnostic: if Comet works only in Global mode, your selected node is probably usable and your Rule list is incomplete or incorrectly ordered. Do not leave Global mode enabled permanently unless you genuinely want all applications to use the same exit. Global routing can unexpectedly affect banking pages, internal company tools, package registries, video calls, and local network devices.

System proxy mode is often enough for the browser if Comet runs inside a conventional Chromium process. If the browser ignores the system setting, or if DNS requests appear to bypass Clash, test the client’s TUN mode where available. TUN captures traffic at the operating-system layer and can cover applications that do not understand HTTP proxy variables. It also has a wider blast radius: confirm that local network access still works, keep an eye on DNS behavior, and disable other VPN software while testing so two virtual adapters do not compete for routes.

3. Map Comet traffic instead of copying a random domain list

A domain list copied from a forum is only a starting hypothesis. Product infrastructure changes, and one user’s account, browser extension, or corporate identity provider may produce a different set of requests. Open a clean browser profile, open developer tools, select the Network panel, and reproduce one complete workflow: load Comet, sign in, open a new conversation, submit a short harmless prompt, wait for the answer to finish, and open one citation. Filter by Doc, Fetch/XHR, and WebSocket, then note the hostnames associated with failed requests.

Look for several categories rather than one magic hostname. The main Perplexity or Comet application host serves the user interface. Authentication hosts handle account redirects and session checks. Static asset hosts deliver JavaScript, stylesheets, fonts, and icons. API or streaming hosts carry prompt requests and incremental answer data. Search, citation, image, and file hosts may appear only after you use a particular feature. If a request is shown as blocked, pending forever, or repeatedly reset, copy its hostname and compare it with the rule that Clash applied in the Connections panel.

Clash Verge’s connection view is especially useful here. Open it while reproducing the problem and check whether the request was sent through the intended proxy group, resolved to an unexpected address, or matched a broad rule such as GEOIP,CN,DIRECT before it reached your AI rule. A browser can report “network error” even when only one supporting JavaScript bundle failed. Conversely, a page may render successfully while the streaming endpoint is still using a weak direct route. Always compare the entire waterfall, not just the first document request.

Symptom Likely layer Useful check
Sign-in returns to the same page Cookies, OAuth redirect, or inconsistent route Use a clean profile and inspect account-related requests
Blank Comet interface Static asset or script request failed Check failed JavaScript and CDN requests in DevTools
Answer starts, then stops Streaming connection, timeout, or unstable node Watch WebSocket or streaming requests in Clash Connections
Citations or images do not load Secondary API or media host is unmatched Open the failed request and add only the observed domain

Avoid adding an enormous catch-all rule simply because it makes one test pass. A broad rule can hide the real cause, route unrelated traffic through a distant server, and make later diagnosis harder. Add a narrow domain rule when the evidence supports it, then retest from a fresh browser session. If the hostname is shared by many unrelated services, prefer a more specific rule or use the profile’s existing provider-maintained policy group instead of guessing at a suffix.

4. Build split routing for Comet and keep local work direct

Once you have observed the traffic, place the Comet-related rules above broad regional, geographic, or final catch-all rules. Rule order matters: Mihomo evaluates the list from top to bottom, so a later AI rule cannot override an earlier broad GEOIP or MATCH decision. Keep your own changes in a small override file if your provider supports it. That makes updates easier to review and prevents a subscription refresh from silently deleting your troubleshooting work.

A conceptual rule structure might look like this:

rules:
  - DOMAIN-SUFFIX,example-perplexity-host.com,Comet
  - DOMAIN-SUFFIX,example-auth-host.com,Comet
  - DOMAIN-SUFFIX,example-stream-host.com,Comet
  - DOMAIN-SUFFIX,company.internal,DIRECT
  - DOMAIN-SUFFIX,local,DIRECT
  - GEOIP,LAN,DIRECT
  - MATCH,Final

The hostnames above are placeholders, not a universal Comet list. Replace them with domains observed in your own browser and profile. The group name must match a real proxy group in your active configuration. Some subscriptions name it Proxy, 手动选择, Global, or something provider-specific. If Clash rejects the file, check indentation, commas, group names, and whether the subscription allows custom rules.

Place private resources and local devices on direct routes where appropriate. Typical examples include internal company suffixes, your router address, local printer pages, development servers, and package registries that your organization requires to stay on its corporate path. Do not blindly mark every Google, Microsoft, or identity domain as direct or proxied. A work account may use an external identity provider, and sending that authentication flow through an unfamiliar relay can violate security policy or trigger additional verification.

After saving the rules, reload the configuration and confirm the active profile. Then clear only the relevant browser site data, not your entire password store. Open a private window or a separate browser profile and repeat the test. In the Clash connection panel, verify that the main application, authentication, streaming, and citation requests are consistently assigned to the intended group. If only one request uses DIRECT, investigate that host rather than switching everything to Global mode.

5. Diagnose sign-in loops, blank pages, and slow answers

Sign-in errors and repeated redirects

First, check the system clock. An incorrect date can invalidate cookies, TLS checks, and short-lived authentication tokens. Next, disable conflicting extensions such as aggressive ad blockers, privacy filters, or another proxy extension. Test a clean profile with JavaScript enabled and third-party login prompts allowed according to the provider’s requirements. If the login page loads through one route and the callback returns through another, the session may be rejected; inspect the redirect hosts and make their route consistent.

Do not repeatedly submit passwords while the route is unstable. Multiple failed attempts can trigger security challenges that look like proxy errors. Sign in once from a stable connection, complete any legitimate verification, and then test Comet again. If a corporate SSO page is involved, ask your administrator whether that identity flow must remain on the company VPN or direct route. Clash configuration should not override an organization’s authentication controls.

Blank pages and missing interface elements

A blank page often means the document loaded but a required JavaScript bundle, font, or API bootstrap request did not. In DevTools, check the Console for blocked scripts and the Network panel for status codes such as 403, 408, 429, or 5xx. A 403 may be an account or provider decision, while a timeout or connection reset points more strongly toward routing or relay quality. Clear the site cache after changing rules, because a cached failed service worker can continue serving an incomplete shell.

If the page works in a clean profile but not your normal profile, restore extensions one at a time. If it fails in every browser, compare system proxy and TUN behavior. A Chromium browser may obey the operating-system proxy while another application uses its own network stack. This is why “the browser works” does not prove that a separate Comet helper, updater, or file-handling process uses the same path.

Slow or incomplete AI responses

Measure more than the time before the first token. Record the time to load the interface, submit a prompt, receive the first streamed text, complete the answer, and open citations. A server with a fast handshake but repeated packet loss can feel worse than a slightly slower server that maintains a clean stream. Test two or three nodes at different times of day and avoid drawing conclusions from one request.

If the answer stops consistently after a fixed interval, examine idle timeouts, connection resets, and WebSocket status in the Clash log. Try another proxy group and temporarily disable browser extensions that inspect or rewrite streaming responses. Do not increase every timeout blindly; long timeouts can leave dead connections consuming resources. If only large prompts fail, test a short prompt and a small file first. Upload size, provider limits, browser memory, and relay bandwidth can all contribute to the symptom.

DNS deserves separate attention. Fake-IP mode can improve performance in some environments but may confuse software that expects the original address, while redir-host mode can expose different resolution behavior. Change one DNS option at a time, restart the browser, and repeat the same workflow. Record the original setting so you can revert quickly. A reproducible before-and-after test is more valuable than changing DNS, TUN, mode, and node selection simultaneously.

6. A repeatable checklist for daily use

Before a work session, confirm that Clash Verge shows the intended profile and that its subscription has not expired. Check the selected group rather than assuming an automatic selector picked the same node as yesterday. Open Comet in the profile you tested, verify that the interface is complete, and send a short non-sensitive prompt. If the answer streams normally, you can proceed with ordinary work. This quick check catches expired subscriptions and dead nodes before you paste important research into a failing session.

Keep a small troubleshooting note containing the date, client version, Mihomo core version, active profile, selected node, browser version, and the failing hostname. Include whether the failure affected sign-in, page rendering, streaming, or citations. Such a record helps you distinguish a provider outage from a local configuration regression. When the product changes its infrastructure, refresh the hostname inventory instead of preserving obsolete rules forever.

  • Use a clean browser profile when testing a new rule.
  • Change one variable at a time: mode, node, DNS, or rule order.
  • Keep sensitive prompts and account tokens out of public logs and screenshots.
  • Prefer the narrowest domain rule that solves the observed request.
  • Return to Rule mode after a Global-mode diagnostic.
  • Remove temporary rules when the provider publishes a maintained policy group.

If the service remains unavailable after a stable route, clean browser test, and correct account setup, stop treating it as a Clash problem. Check the provider’s status page, account notices, regional availability, usage limits, and supported browser requirements. A well-configured proxy cannot fix a suspended account, an exhausted quota, a server-side incident, or a feature that has not been enabled for your account.

7. Frequently asked questions

Do I need Global mode to use Perplexity Comet?

No. Global mode is a useful diagnostic because it quickly shows whether a selected node can reach the service, but Rule mode is safer for regular use. With Rule mode, you can send observed Comet, authentication, streaming, and citation domains through a suitable group while keeping local and work-related traffic on its required route.

Should I enable TUN mode?

Enable TUN only when system proxy mode does not capture the traffic you need, or when a supporting process ignores ordinary proxy settings. TUN can cover more applications, but it also changes DNS and routing for a wider part of the system. Disable other VPN clients, confirm local network access, and test one workflow at a time after enabling it.

Why is the lowest-latency node not always the fastest?

Latency is usually measured with a short probe, while Comet may maintain long-lived streaming connections and several parallel requests. Packet loss, congestion, relay bandwidth, and idle timeouts can make a low-ping node perform poorly during a complete answer. Compare time to first token, completion time, and connection stability instead of relying on ping alone.

Can I use a copied Comet domain list?

Use copied lists only as an initial reference. Hostnames and product flows change, and your account or identity provider may add different requests. Verify every important rule in DevTools and Clash Verge’s connection logs, remove obsolete entries, and avoid broad catch-all rules that route unrelated traffic through the proxy.

Many one-click VPN tools are convenient for a quick browser test, but they often provide little visibility into why a page is blank, why authentication loops, or why streaming stops after the first sentence. Compared with those binary switches, Clash Verge offers observable connections, selectable nodes, ordered domain rules, and a practical split-routing model: Comet can use a stable relay while local services and corporate resources stay on their expected paths. If you want to reproduce this setup across Windows, macOS, Linux, or Android with a Mihomo-compatible client, the next step is to choose the appropriate package and profile rather than keep guessing at browser toggles.

Download Clash clients →

Ready to get started?

Get a Mihomo-compatible Clash client and build a more predictable routing setup for Comet and other AI services.