# Eggent for Mac > The Eggent app for Mac: what it is, how to download it and open it the first time (it is not signed yet), where its files live, and how to update or remove it. Source: https://eggent.ai/docs/desktop-app/ Eggent for Mac runs the same agent as Eggent Cloud on your own computer. Your projects are ordinary files in a folder you can open in Finder, and the agent works with the programs and files on your Mac. Connect your cloud workspace and the Mac and the cloud become one agent: [the same files, chats and memory on both](https://eggent.ai/docs/desktop-cloud.md). > [!WARNING] > This is an **early build** for Apple silicon, and it is **not signed or notarized by Apple yet**. macOS will not open it the first time without your say-so ([how](#first-launch)). Use it at your own risk, keep a copy of anything you can't lose, and read [what the agent can reach](#access) before you start. ## What it is {#what} An app with the same screens as the cloud version, and the Eggent server running inside it, on your computer. The server listens only on a local address, and only the app's window can talk to it. It works in two ways, and you can switch between them at any time: - **On its own.** Everything stays on this computer. You bring the model: a provider key of your own, or a program you already have ([Working on your own subscription](https://eggent.ai/docs/desktop-programs.md)). - **With your cloud workspace.** The Mac and the workspace are one agent, and the AI included in your workspace works here too: see [The app and your cloud workspace](https://eggent.ai/docs/desktop-cloud.md). ## Download {#download} Download the current build from the [Eggent for Mac page](https://eggent.ai/mac/). The page shows the size of the file and its SHA-256 checksum. After downloading, compare it: ```bash shasum -a 256 ~/Downloads/Eggent--arm64.dmg ``` ### What you need {#requirements} - A Mac with **Apple silicon** (M1 or newer) and **macOS 13 (Ventura) or later**. Intel Macs and Windows are not supported yet. - About **1.2 GB** of disk space for the app (the download is about 360 MB), plus room for your projects. - An internet connection for the model, whether it comes from your cloud workspace or from your own provider. - Optional: **Python 3** for the terminal panel. It comes with Apple's command line tools (`xcode-select --install` in Terminal). ## Open it the first time {#first-launch} macOS opens an app without a warning only after Apple has checked it, and that needs a paid developer certificate which Eggent does not have yet. So the first time you open the app, macOS stops it. Nothing is wrong with the file: you allow it once, and macOS remembers. 1. Open the `.dmg` and drag **Eggent** into **Applications**. 2. Open Eggent from Applications. macOS says it can't verify the app is free of malware. Click **Done** (**OK** on older macOS). 3. Open **System Settings → Privacy & Security**, scroll down to **Security**, click **Open Anyway** next to Eggent, and enter your password or use Touch ID. 4. Open Eggent again and click **Open**. This is the way Apple describes for any app macOS blocked: [Safely open apps on your Mac](https://support.apple.com/en-us/102445). A new download of a newer build asks again. On macOS 13 and 14 you can also Control-click Eggent, choose **Open**, and confirm. If you prefer Terminal, remove the "downloaded from the internet" flag and open the app as usual: ```bash xattr -dr com.apple.quarantine /Applications/Eggent.app ``` > [!NOTE] > If macOS says Eggent is **damaged** and offers to move it to the Trash, check the checksum of the file you downloaded (see [Download](#download)). If it matches, the file is fine: run the Terminal command above and open the app again. If it does not match, download it again. ## The first run {#first-run} 1. **Where should Eggent live?** Pick a folder; the default is `~/Eggent`. Everything Eggent does and keeps goes inside it. A folder that already has other things in it is never filled: Eggent makes a subfolder and says so first. If Eggent is already in the folder you pick, the app connects to it and deletes nothing. 2. **Connect cloud Eggent?** Enter your workspace name, login and password to connect your cloud workspace ([how it works](https://eggent.ai/docs/desktop-cloud.md#connect)), or press **Not now** and connect later from the **Eggent menu → Cloud & Sync…**. **I don't have an account yet** opens the cloud sign-up page in your browser; come back and connect afterwards. 3. The app prepares the agent's tools, starts the server and opens the window. The first start takes longer than the later ones. You never type a password on your own computer: the app signs its own window in. Without a cloud account the app needs a model. In **Settings → Models** add a provider with your own API key, or use [a program already on your computer](https://eggent.ai/docs/desktop-programs.md). ## Where everything lives {#folder} ```text ~/Eggent/ Projects/ shortcut to data/projects: your projects and the agent's files data/ projects/ projects and the agent's files chats/ what the screen shows of each chat pi-sessions/ what the agent remembers of each chat chat-files/ attachments settings/ … keys and settings of this computer README.txt ``` **File → Show Eggent Folder in Finder** and **File → Show Projects in Finder** open them. The app's own settings are in `~/Library/Application Support/Eggent`, and **File → Show Log** shows where its log is. **File → Change Eggent Folder…** puts it somewhere else, in one of two ways. **Move** takes everything to the new place: projects, chats, the agent's memory, the sign-in and the cloud connection. **Open Another** makes Eggent work in another folder and leaves this one on disk as it is: an empty folder starts afresh, an Eggent folder opens with what is in it. With the cloud connected, that other folder is kept in step with it: what is in it goes to the cloud, and the cloud's projects and chats come to it. Wait for the agent to finish what it is doing first; the app stops for a moment and starts again. Keys and settings are this computer's own. They are never synced to the cloud. ## Models {#models} The app needs a model to answer. There are three ways to give it one, and you can mix them: - **Your cloud workspace's AI.** Once you [connect the workspace](https://eggent.ai/docs/desktop-cloud.md#connect), the included models appear in **Settings → Models** and are counted on the same balance as in the cloud. They never replace a provider you chose yourself. - **Your own provider.** **Settings → Models** takes an API key, the same as on a server you run yourself: see [Models](https://eggent.ai/docs/models.md#own-provider). - **A program already on your computer.** A project can run on Claude Code or Codex with your own subscription: [Working on your own subscription](https://eggent.ai/docs/desktop-programs.md). ## What the agent can reach {#access} In the cloud the agent works inside a computer that holds only your workspace. **On your Mac there is no such box.** The agent has a terminal and runs commands as your user, starting in the Eggent folder, so it can read and change anything your account can, just like any program you run. What keeps it in check: - Only the app's window can talk to the local server. A web page open in your browser cannot, even though the server is on your own machine. - The server gets a small, fixed set of environment variables, not the ones in your shell, so keys you exported in Terminal are not handed to it. - Keys and settings you add stay in the app's data folder and are never synced to the cloud. Treat the agent the way you would a capable assistant with a terminal on your laptop: ask for things you would be comfortable with it doing, and keep important data backed up. ## Updates {#updates} There are no automatic updates yet. To update, download the new build from the [Eggent for Mac page](https://eggent.ai/mac/), quit Eggent, drag the new Eggent into **Applications** and replace the old one, then open it. macOS asks for permission again, as the first time. Your folder and settings stay as they are. Keep the app reasonably current if you use it with the cloud: they share chat files, and versions far apart may not read each other's. ## Remove it {#remove} Quit Eggent and drag it from **Applications** to the Trash. That leaves two things behind on purpose: your `~/Eggent` folder, which holds your files and chat history, and the app's own settings in `~/Library/Application Support/Eggent`. Delete them too for a clean slate. If you used the cloud, [disconnect](https://eggent.ai/docs/desktop-cloud.md#disconnect) first. ## If something goes wrong {#troubleshooting} - **macOS will not open the app, or says it is damaged.** See [Open it the first time](#first-launch). - **"Eggent didn't start".** The screen offers **Try again** and **Show log**. The log says what happened; if you write to support, include it. - **The first start is slow.** The app prepares the agent's tools once, which takes a minute or so. Later starts are quicker. - **The terminal panel says it is not available.** It needs Python 3; install Apple's command line tools with `xcode-select --install`. Commands still run from the chat meanwhile. - **"Eggent is still working" when you quit.** The app counts the chats that are running now. If you quit, they stop; **Keep working** lets them finish. - **Sync problems.** See [The app and your cloud workspace](https://eggent.ai/docs/desktop-cloud.md#troubleshooting). ## Not here yet {#limits} - Windows and Intel Macs. - Signing and notarization, so no warning on first launch, and automatic updates. - Starting at login and a menu bar item. - The speech recognition and the Python document tools that the cloud's computer carries. The agent uses whatever you have installed. - Schedules that run while your Mac is off. A schedule made in the app runs only while the app is open; for a task that must run on time, create it in the cloud. See [What stays on each side](https://eggent.ai/docs/desktop-cloud.md#separate).