Models

The model is the agent's brain: it reads your task, decides which tools to call and writes the answer. The model decides the quality, speed and cost of the work.

#Eggent AI

The cloud comes with Eggent AI connected — a catalog of models from several families: GPT, Claude, Gemini, DeepSeek, GLM, Kimi. No keys needed: every model is paid for from one workspace balance.

• Prices are per million tokens, separately for input, cached input and output. The price table is on the billing page and in Settings → Models.
• Prices are based on the model makers' published prices, so you can check them.
• Cheaper models make the balance last longer; stronger ones handle hard work better. The same job can run on different models in different projects.

Every model in the list is available, on the trial as well. If an installation restricts part of the list, the rest is visible but disabled, with a note on how to open it. See Plans and balance.

#Changing the model

Quickly, right in the chat. Left of the send button is the model's name. Click it, find a model with the search and pick it. Models are grouped by family.

• Inside a project, the choice is saved for that project.
• In the orchestrator, for the whole workspace and every project without its own model.

The line shows which model will answer the next message.

In settings. Settings → Models → Workspace model: provider and model. Under Advanced are the thinking level (how much the model reasons before answering), image generation and editing models.json by hand.

#A project's model

A project can have a model of its own: a cheap one for bulk work, a strong one where it pays off. In Settings → Models, switch the scope in the top right to the project and choose:

• the workspace model — the project answers with the same model as the orchestrator;
• its own model — from the providers that can answer right now.

While the workspace runs on Eggent AI, a project chooses among Eggent AI models. If a project's saved model cannot be used (its provider was disconnected, say), the project quietly answers with the workspace model.

#Your own provider

You can work on your own key — OpenAI, Anthropic, Google, OpenRouter, DeepSeek or any service with an OpenAI-compatible API, including your own local model on your own server. Requests then go straight to the provider at its prices, and the Eggent AI balance is not spent.

1. Settings → Models → Use my own provider.
2. Pick the provider.
3. Paste the API key and press Save key. Some providers offer sign-in with a subscription instead of a key.
4. Pick the model. Eggent tells you which model the workspace now answers with.

A provider that is not on the list is easiest to add through the agent: write "connect the provider at https://…/v1 with the model …". The agent registers it, and you paste the key in settings. The other way is Advanced → Custom providers and models, where models.json is edited.

If a key does not work or an address is unreachable, Eggent says exactly what is wrong: the address does not answer, the key was rejected, or the provider has no such model.

#On this computer

In the Eggent app for Mac, a project can also run on Claude Code or Codex already installed on the computer, with your own subscription instead of a model: see Working on your own subscription.

#Images, voice and memory

While the workspace runs on Eggent AI, it also draws images, turns voice into text and runs the short look-back after a reply that keeps what the agent learns. When you move to your own provider, all three stop using Eggent AI, so nothing more is spent from its balance:

• images are off until you choose who draws them;
• voice is transcribed by Whisper on the workspace's own server;
• the look-back runs on the chat's own model.

In Settings → Models → Advanced → Images, voice and memory you can turn Eggent AI back on for any one of them — keep your own model for the chat and Eggent AI for voice, say — or point images and voice at a provider of your own. That has to be a provider connected with an API key: a subscription sign-in has no key to send.

Leaving Eggent AI again turns it off for all three, and a project that was put on an Eggent AI model follows your new model. Its last choice is remembered in the project's model settings, so putting it back is two clicks.

#Back to Eggent AI

In Settings → Models, press Use Eggent AI again. No key needed, it is one click, and images, voice and the look-back go through it again. Your own providers' keys are kept, so you can go back to them too.

#Your own server

The open core has no Eggent AI: on first launch connect a provider in settings or set a key in an environment variable (OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, OPENROUTER_API_KEY). See Configuring your server.