Solfox guide
After reading about the Solfox fingerprint browser, use this guide to get started with your Solfox delivery.
Confirm the account and its environment before opening your service.
What is Solfox?
Solfox is a fingerprint browser client developed by Supakook using Camoufox. It manages separate browser environments for SaaS accounts. Windows, macOS, and Linux are supported; check your delivered version for specific OS versions, processor architectures, and installation requirements.
Solfox manages browser environments. Membership benefits belong to the account and order, while API keys are used in API clients. These are separate parts of your setup.
Before you begin
Get the installer and instructions through the Solfox product page or your original order channel. A public download URL is still pending; follow the installation instructions for the version you receive.
Check these four items when your delivery arrives:
| Item | What to confirm |
|---|---|
| Installer | Matches your OS, processor architecture, and version requirements |
| Service and account | Product, membership plan, and account ownership |
| Environment | Whether to use a delivered environment or prepare one using the instructions |
| Sign-in and verification | Service entry point, who completes verification, and which account settings you may change |
If the account-to-environment mapping is missing, ask your original order channel to clarify it. Do not try another person's environment or credentials.
First use
1. Install and open the client
Follow the delivery instructions to install the version for your system, then start Solfox. Record the client version for any later support request.
If it will not start, keep the error message and check whether the installer matches your system. Avoid deleting existing environments or repeatedly reinstalling as a first step.
2. Confirm the environment for your account
Open the delivered environment as instructed. If you need to prepare your own, follow the guide for that release.
Use a mapping like this to record your setup. These labels are examples, not actual client buttons or features:
| Service | Account type | Environment |
|---|---|---|
| ChatGPT | Your own account | That account's ChatGPT environment |
| Claude | Delivered account | That account's Claude environment |
| Shared ChatGPT | Subject to sharing rules | Environment specified in the delivery instructions |
Keep using the original environment for each account. Do not mix different accounts' sign-in data in one environment or casually share environment files.
3. Sign in and check the membership
Use the service entry point in your delivery instructions. Check the signed-in account, then confirm that the membership matches your order.
- ChatGPT: Check Web and required features against your plan's delivery instructions.
- Claude: Check the membership tier and verification requirements in the Claude guide.
- TradingView: Check the plan and active status in the TradingView Premium guide.
If verification appears, follow the account's normal verification process. If you cannot complete it, keep the message and contact your original delivery channel. Do not repeatedly try unknown codes or credentials.
4. Try a simple task
Open an ordinary page or send a simple message without private information to check that the service works.
Close and reopen the environment, then check that it still opens the expected account. If sign-in expires or verification repeats, record the behavior before troubleshooting; avoid immediately creating multiple replacement environments.
Everyday use
Keep track of three things: the service, the signed-in account, and the open environment.
- Check the current account before starting, especially when using several plans.
- Follow release instructions for updates, and read migration requirements first when an update affects environments.
- Change one setting at a time during troubleshooting so you can identify what helped.
- Save error details before dealing with sign-outs or verification. Do not immediately clear all cookies and local data.
Extra checks for shared plans
Separate browser environments isolate local browser data. They do not automatically isolate chats, files, or account settings stored by the service within the same shared account.
Confirm conversation visibility, concurrency rules, and permission to change settings in your order instructions. Separate local environments alone do not make data within one account private to each person.
See Privacy and data for related boundaries.
Changing devices or networks
Before moving to another computer, check whether your release supports environment migration and what requires sign-in or verification again. This guide does not assume that cloud sync, automatic migration, or backups are available.
- Save your work and record the account-to-environment mapping on the old device.
- Prepare the new device as instructed. Keep the old environment until the new one works.
- Use only migration methods supported by that release. Do not casually send a whole environment directory to someone else.
- Check the account, membership status, and normal operation on the new device.
For a network change alone, first check access using the original browser environment. Complete account verification if requested. Avoid changing the network, rebuilding the environment, and editing sign-in information all at once.
When something goes wrong
| Issue | First check | Include in your report |
|---|---|---|
| Client will not start | Installer, OS, and version requirements | OS version, Solfox version, exact error |
| Environment opens but the site does not | Network and target service availability | Target service, time, page message |
| Repeated sign-outs or verification | Account, environment, and recent device or setting changes | Verification type and behavior before and after the change |
| Membership differs from the order | Signed-in account and membership status | Order number and redacted membership screenshot |
| Answer quality changes | Model name, time, and a simple reproducible prompt | A non-confidential example; see Quality checks |
Contact your original order or delivery channel. Keep only necessary details in screenshots and logs, and hide passwords, verification codes, cookies, API keys, and private conversations.