Eigent is an open-source “coworker” agent that runs directly on your desktop. It uses a multi-agent architecture to perform browser automation, terminal automation, and file system operations, acting much like a human worker operating in a real desktop environment.Because Eigent interacts heavily with your local machine, routing its traffic through LLM Router is highly recommended. It ensures that any local .env files or API keys it accidentally reads are redacted before reaching external LLM providers, and it compresses bloated terminal/browser outputs to save you massive amounts of input tokens.
Important: When using LLM Router with Eigent, you must configure the
Custom API Host to point to https://api.llmrouter.app/v1 to ensure API
compatibility.
In the Settings menu, find and select the Models section. Scroll down to the Custom Model area and look for the configuration card (often labeled as Custom OpenAI Config or similar).
With the configuration complete, your Eigent agents are now powered by LLM Router.Because Eigent executes tasks autonomously on your machine, the safety and cost-saving layers of LLM Router become critical:
Zero-Trust PII Redaction: If an Eigent agent reads a local config file containing your AWS keys or Stripe tokens while trying to debug a project, LLM Router will automatically mask them into [TOKEN_REDACTED] before sending the context to Claude or GPT-4o.
Context Pruning: Agents often “loop” and read the same files multiple times. LLM Router will intelligently compress the middle of these repetitive file reads, saving you thousands of tokens per task.
Provider Resilience: If Anthropic goes down while Eigent is in the middle of a complex multi-step browser automation task, LLM Router will seamlessly fall back to OpenAI, preventing the agent from crashing and losing its progress.