Skip to main content
Below are illustrated answers to common questions — scroll to find yours. If your question isn’t listed, check the corresponding feature page in this handbook for details.
Still stuck? Email team@soloent.ai with the following:
  1. Your login account (email address)
  2. Your client version number
  3. Detailed steps to reproduce
  4. Relevant screenshots

The login redirect prompt does not appear

After authorization succeeds, the browser usually asks whether to open SoloEnt, and there is a backup button at the bottom of the page:
  • In the popup, choose Open SoloEnt to allow the desktop app to open
  • If there’s no popup, click Click here to open SoloEnt on the page to trigger it manually
Authorization success page: the browser asks whether to open SoloEnt, with the Click here to open SoloEnt backup button on the page If there’s still no response, the browser is most likely blocking the popup. In Chrome, for example: Settings → Privacy and security → Site settings (which controls a site’s use of location, camera, pop-ups, and more), then allow pop-ups and redirects for account.soloent.ai. Chrome settings: Privacy and security and the Site settings entry In Site settings, turn on Pop-ups and redirects, set SoloEnt’s sites to allowed, and retry the login. The Pop-ups and redirects option in Site settings, set to allow sites to send pop-ups and use redirects

Can’t find the recharge/upgrade entry

There are two ways to reach the subscription console: Reaching the console via Dashboard from the account avatar menu
  • Option 2 (from v0.3.5): Click the Agent Settings in the top-right → API settings; there’s an upgrade-to-VIP prompt and entry above the free model list.
Opening API Configuration in Settings, with the Upgrade subscription button below the free model list Once in the web console (Dashboard), switch to the Subscription Plan tab and choose your plan (Lite, Pro, or Max) and billing cycle (monthly or yearly). Choosing a plan and billing cycle under the Subscription Plan tab in the console

Can I get a refund? What if I run out of credits?

In the console, the button for your currently active plan shows Cancel subscription; click and confirm to cancel.
  • After canceling, the current period is not refunded; your benefits continue until the period ends and it won’t auto-renew.
  • If your subscription credits run out, you can upgrade to a higher tier, or buy add-on credits separately (note: without an active membership you cannot top up credits directly).
The console Subscription Plan page: the Cancel subscription and Buy add-on quota entries under the Lite plan
Add-on credits apply only within the current billing cycle. When your subscription renews next month or you make a subscription change (upgrade, downgrade, switch period), your quota resets to the plan’s base amount, and top-up credits do not carry over.
For more on managing your subscription, see Manage subscription and Make the payment.

How do I configure a third-party API key?

SoloEnt supports BYOK for free. Just select BYOK on the API settings page, then choose your API provider from the dropdown. Selecting BYOK in API settings and choosing a provider from the API Provider dropdown Most third-party providers’ keys need to be configured via OpenAI Compatible. You must fill in all three fields:
  • Base URL
  • API Key
  • Model ID
Under BYOK, API Provider set to OpenAI Compatible, with Base URL, API Key, and Model ID to fill in If it doesn’t work after configuring, first check that all three are entered correctly. Confirm with your provider before purchasing, as some third-party services can be unstable. Most official providers’ APIs can also be configured via OpenAI Compatible, as long as the Base URL you enter is correct.
If you use a third-party API, we cannot help resolve API call errors. When you hit errors, try switching to a more stable API.
For details, see API Configuration.

The Agent panel language isn’t what I want

SoloEnt is the international edition. After you change the interface language on the welcome page, only some prompts in the main window change. The right-side Agent’s language must be set separately. The Language and Theme options in the top-right of the welcome/main interface Click the settings icon in the top-right of the Agent panel and configure, under General Settings:
  • Preferred Language: the language the AI replies in — the language you receive responses in when chatting with the Agent
  • Interface Language: the display language of the Agent panel itself (menus, buttons, etc.); supports 简体中文, English, 日本語, 한국어, Español
The Preferred Language and Interface Language options under the Agent panel's General Settings

The Agent won’t create/save files, or always asks me to save

Check the following two settings in order. 1. Auto-approve
In the Auto-approve settings at the bottom-right of the Agent window, allow auto-edit so the Agent can write to project files without your approval.
If it’s off, every file write needs your confirmation. See Auto-approve. Permission toggles for reading and editing project files in the Auto-approve settings 2. Background Edit In Agent Settings → Tool settings (the second item on the left), the Background Edit toggle under the Editor block controls whether files can be edited in the background without taking editor focus. If you always want to review before revising, keep this off. Otherwise the Agent may modify files without your noticing. The Background Edit toggle in the Editor block of Feature Settings

Prompt to install Git (for checkpoints)

The first time Windows users open SoloEnt, they may see the prompt shown below. It’s because Git isn’t installed, but it doesn’t affect normal use. Git is used to save state checkpoints during a conversation so you can roll back to a checkpoint and start over. macOS usually ships with Git; Windows usually needs a manual install. If you don’t need checkpoint recovery, you can ignore this prompt for now; when you do need it, download and install from git-scm.com. The Git and checkpoints prompt banner in the SoloEnt panel (Git must be installed to use checkpoints)

What is the context window? When should I open a new one?

Every session window has a context-length limit. Above the chat box you can see the current window’s session ceiling and how much context is used — for example the 30.2k / 300.0k below: the left number is the tokens used, and the right number is the current session’s context ceiling. The context progress bar above the SoloEnt chat box, showing 30.2k used and a 300.0k ceiling When a lot of context is used, the model’s memory of earlier content gets fuzzy and it tends to drift on long tasks. And bigger isn’t always better — an oversized window scatters the model’s attention and pushes up cost, so keep the session ceiling around 200K–300K. Consider opening a new window when:
  • The current task is done and you’re starting a separate one
  • A single window has reached about 100–150K (continuing past 200K may cause a cost surge)
  • You’re switching to a new direction unrelated to the current topic
As a rule of thumb, once a single window passes 100k, it’s worth opening a new one.
Before opening a new window, you can use /compact to condense the current session into a short summary, or have the Agent summarize the key points into SOLOENT.md, so the new window quickly restores context instead of piling up tokens from scratch. For details, see Using the Context Window Wisely and the SOLOENT.md Guide.

Why doesn’t my project generate SOLOENT.md automatically anymore?

As of v0.2.0, SOLOENT.md is no longer generated automatically. You can create it manually at any stage of a project with the /init command, or skip it entirely for short pieces or when you don’t need context tracked across sessions.

Why do files sometimes fail midway or get regenerated repeatedly?

Common causes include:
  • The write was interrupted by hand: while the Agent is editing a file, editing it yourself, closing the Agent’s edit box, or making changes while the model is thinking can all cause duplication or truncation
  • BYOK model output is truncated: a third-party model’s max output length may be capped, so the truncated result makes the file-writing tool call fail
  • The client is outdated: older clients support newer models poorly — check your client version and keep it updated
  • The single-window context is too long: when context is too long, the model’s tool-call output can be malformed. Tidy up your SOLOENT.md memory file and continue in a new session, rather than staying in one session indefinitely