Eigent

Eigent: Fixes

This page covers the problems people hit most often with Eigent, drawn from its docs, its release notes, and its GitHub issues. It is the sixth of eight pages. Each problem gives the symptom, the likely cause, and the fix, in that order.

These notes match version 1.0.7 as checked on 14 November 2026. If you need to stop Eigent right now, jump to "Stop it right now" below.

Get the logs first

For most problems, Eigent can save its own logs for you or for its support team. The v1.0.7 app has a Download logs area with two files. The Eigent log holds the "Desktop app logs," and the Camel log holds the "Agent task logs (CAMEL backend)" for each task.

The app also has Report a bug. In the app's words, it will "save a ZIP of app logs, then open your email app" so you can send it. Logs can hold file names and parts of your tasks, so read them before you post them anywhere public.

Problems

The app stalls while it starts for the first time

Symptom: after the install, Eigent opens but sits on a loading screen. In one open GitHub report, it stays at 80% with no logs showing.

Likely cause: Eigent sets up a local backend the first time it starts, and that setup can fail. On Windows, a maintainer called one such failure in version 0.0.82 a known issue, where the app's built-in setup failed and could not repair itself. Version 1.0.5 started shipping Git inside the Windows x64 app, which its release notes say was done "to prevent backend startup failures when Git is not installed."

Fix: quit Eigent and open it once more, then make sure you have the newest version from the release page. If it still stalls, follow the clean reinstall in "Uninstall or reset Eigent cleanly" below, which is the step a maintainer gave for the Windows failure. This guide could not confirm a fix for the 80% stall, because that GitHub issue was still open on 14 November 2026.

The login never finishes

Symptom: you sign in on the web page that Eigent opens, and the sign-in works there. But the app keeps showing "Logging in..." or returns to its login screen.

Likely cause: the app does not receive the sign-in back from the browser. Two GitHub reports describe this, one on Windows 11 with version 1.0.2 and one on macOS. Both were still open on 14 November 2026.

Fix: quit Eigent fully, open it again, and try the login once more. If it still fails, use Report a bug so the team gets your logs. This guide could not confirm a reliable fix, and since Eigent needs an account, you cannot use the normal app until the login works.

Save says "Invalid key" or "Invalid model name"

Symptom: when you click Save on a model card, Eigent shows one of two messages. They are "Invalid key. Validation failed." and "Invalid model name. Validation failed."

Likely cause: the docs give a cause for each. A bad key "is incorrect, expired, or malformed," while a bad model name means the model "does not exist or is not available for your account" at that provider.

Fix: for a bad key, copy the key again from the provider's site, with no extra spaces, or make a new one. For a bad model name, copy the exact name from the provider, such as Google AI Studio for Gemini, because a free key may not reach every model. The models page also says to check the endpoint, the provider region, the API version, and any network proxy.

The answers stop with a quota or rate-limit error

Symptom: a job that worked earlier now fails. Eigent may show "You exceeded your current quota" as the error.

Likely cause: the docs give "API quota exhausted or billing issue" as the cause of that message. On a free key it usually means you hit the provider's rate limit or daily free tier. On Eigent Cloud, it means your credits ran out.

Fix: on a free key, wait and try the job again later, and send smaller jobs so each one uses fewer tokens. On a paid key, check the provider's billing page. Version 1.0.7 adds a notice for running out of Eigent credits. It lets you "switch to your own API key straight from the notice," which is the way back to $0.

A local model cannot be reached

Symptom: you chose Ollama or another local program, but Eigent cannot validate it, or no local models appear.

Likely cause: the local program is not running, the address is wrong, or the program does not list its models.

Fix: check the three things the self-hosting page lists, which are that the program "is running, the endpoint includes the expected /v1 path, and the port is accessible from the Eigent process." For Ollama, that address is usually http://localhost:11434/v1. If no models appear, type the exact name you downloaded, because "Some runtimes require entering the model name manually," as the models page says.

The agent loops, repeats itself, or seems stuck

Symptom: the task runs the same step again and again, or it sits for a long time with no new steps and no error.

Likely cause: the job is too broad, or the model is too weak for a long job. A Workforce has a built-in brake. The docs say it halts a workflow when a task "has failed or been decomposed more than a set number of times (default: 3)" so that it cannot loop forever. A Single Agent task has no such counter in the docs, and one open GitHub issue reports tasks that stalled with no error at all.

Fix: stop the task, as below, then send a smaller job. For a task that is too broad, the Single Agent page advises you to "Split the request into smaller Tasks in the same Session or use Workforce mode" instead. If the same job keeps looping, try a stronger model.

Stop it right now

Symptom: the agent is doing something you did not ask for, or you just want it to stop.

Likely cause: none needed, because stopping is always fine.

Fix: while a task runs, the v1.0.7 app shows stop controls labeled Stop, Stop Task, or Cancel task, depending on the view. This guide could not confirm which one you see where. Click Reject on any approval that is waiting.

If the app does not respond, quit Eigent. Know that "Quitting pauses any running tasks. They will be marked interrupted, not cancelled," in the app's own words. When you reopen it, cancel those tasks instead of resuming them.

The app may report "Task stopped locally, but backend notification failed. Backend task may continue running." If you see that, quit Eigent completely. Also click Revoke link for any Remote Control link in Dispatch, and turn off any Automation that might start the job again.

After it stops, use After it does something wrong if a file, account, or charge already changed.

The agent cannot find your file

Symptom: the agent says a file does not exist, or it looks in the wrong place.

Likely cause: the file is outside the folder your Space is connected to, or you are in a different Space.

Fix: the Single Agent page says to attach the file to the task or add it to the Space's working folder. It also says to confirm "that the active Space is connected to the correct folder" before you try again. Copy the file into your tryout folder rather than connecting a bigger folder.

An Automation did not run

Symptom: a scheduled job did not happen at the time you set.

Likely cause: "Scheduled runs require Eigent to remain open on this computer," say the version 1.0.6 release notes. So the computer may have been off or the app closed. The run may also have failed, or hit one of the run limits you set.

Fix: open Automations and check the run history and the execution log, which the docs say show errors and cancellations. You can retry a failed run. Version 1.0.7 adds Run now and says runs the app never received are recovered. Leave the computer on and Eigent open for future runs.

Update it safely

Read the notes on the Eigent releases page before you install anything. A Space made in an older version can become read-only. The v1.0.7 app then tells you to create a new Space before a new session.

  1. Quit Eigent. Copy your settings, memory, and workspace to a second place before you update. Copy the .eigent folder in your user folder. On Windows that is C:\Users\<your name>\.eigent, and on a Mac it is ~/.eigent. It holds the backend setup, skills, browser profiles, memory, and a secure folder. Also copy the Space folder you connected, such as eigent-tryout. Also copy Electron's user-data folder. The updater code calls that the place where config lives. This guide could not confirm its exact name. Look under AppData\Roaming on Windows, or ~/Library/Application Support on a Mac, for eigent or Eigent. A copy can live in Windows File History or Previous Versions, or in Mac Time Machine.

What you should see a second copy of .eigent, your Space folder, and that user-data folder, dated today.

  1. Read the release notes, then use the app's own update button. Version 1.0.7 checks for an update and does not download it until you click. When a new version is ready, the top bar (and the Version row in Settings) shows Update. Click Update, wait until that button says Launch new version, and click it. If Update never shows, download the newer installer from the releases page and run it as you did the first time. The v1.0.7 Windows installer is set not to delete app data on uninstall. These steps do not delete .eigent. If you built Eigent from source, follow "Update a self-hosted installation" on the self-hosting page, and leave .eigent where it is.

What you should see Eigent opens again after the new version installs.

  1. Open Settings, choose Settings, and read the Version row. Then run the first safe job from page 2 again, and leave Ask me first on.

What you should see the Version row shows the new number, and your tryout folder still has the original file plus one new note.

Uninstall or reset Eigent cleanly

Symptom: you want Eigent gone, or a fresh start after a setup that keeps failing.

Likely cause: none needed. Eigent keeps its own files in a folder named .eigent in your user folder. The logs in GitHub issues show it holds Eigent's backend setup, browser profiles, and skills.

Fix: first remove what Eigent can reach outside your computer.

  1. In Dispatch, select Revoke link for any Remote Control link.
  2. Turn off or delete each Automation.
  3. Remove your models. The models page says to open the provider, disable it, and choose delete or reset. That "does not delete the provider account or local model," the page adds.
  4. On the provider's website, delete the API key you gave Eigent.

Then remove the app. On Windows, a maintainer's steps are to uninstall Eigent "via Windows Settings → Apps or the installer" first. Then delete the .eigent folder in C:\Users\<your name>, and reinstall if you want a fresh start. On a Mac, this guide could not confirm official steps. The same folder is ~/.eigent, and the app itself is the Eigent icon in Applications, which you can drag to the Trash.

Deleting .eigent removes Eigent's local setup. This guide could not confirm whether it also removes your Spaces' history and memory, or what stays on Eigent's servers with your account. None of these steps touch your tryout folder, so delete it yourself if you want it gone.

One open GitHub issue reports that deleting a Space can fail with "Failed to Delete Space" as the message. A user said on 7 November 2026 that this still happened in 1.0.7, so if you meet it, delete the tryout folder by hand. This guide could not confirm how to delete an Eigent account. For account questions, the support page gives support@eigent.ai as the contact.

Sources

Checked 14 November 2026.

Next

Continue to Eigent: Advanced features.

Checked 14 November 2026 · prices, limits, and versions change