The app and your cloud workspace

Signed out, the Eggent app for Mac works on its own and everything stays on your computer. Signed in to your Eggent Cloud workspace, the computer and the workspace are one agent: the same files, the same chats, the same memory of each chat, the same attachments. There is no switch between a "local" and a "cloud" agent. Start a chat in the browser, carry on in the app, and the agent remembers.

#Connect

On the first screen ("Connect cloud Eggent?"), or later through Eggent menu → Cloud & Sync… → Connect an account, enter:

• the workspace name: the part before .cloud.eggent.ai (a pasted address is shortened for you);
• the login and password of the workspace, the same you use in the browser.

The app uses them once, to pair this computer with the workspace, and does not keep the password. Pairing adds the computer to the workspace's sync and hands the app a key for the workspace's AI. I don't have an account yet opens the cloud sign-up page in your browser; signing up is not in the app yet.

The sync program is part of the app, so there is nothing to install. It is separate from Files on your computer, which keeps only the projects folder in step through a program you install yourself.

#One agent

These are kept in step, in both directions, even while the workspace is asleep:

• Files: the projects folder.
• Chats: what the screen shows of each conversation.
• Agent memory: what the agent remembers of each chat, so it carries on where it left off on the other side.
• Attachments.
• The task board, for a workspace that lets chats run on either side (see Where a card runs).

The window title tells where sync stands: in sync, syncing 40%, can't reach the cloud, sync problem. Eggent menu → Cloud & Sync… shows the same in full, with what is kept in step. Offline, files are saved here and sent as soon as the connection is back.

#What stays on each side

Never synced, by design:

• Keys and settings. Each side has its own provider keys, login and preferences. Connecting the workspace never moves you off a provider you chose.
• Telegram connections.
• MCP server settings (.mcp.json), because they may hold tokens.
• Schedules. A schedule is armed inside one running agent, and two computers each firing the 7 o'clock job would post twice. The cloud is on while your Mac is off, so schedules that matter live there. 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.

#Room in your plan

The cloud stops the agent when your plan's storage is full, so the app will not fill it by surprise. Files are always sent. Chats, agent memory and attachments are sent only if everything fits; if not, the app asks once, before anything goes:

Your chat history won't fit in your plan. … Keep them here, or Send anyway?

Keeping them here leaves the files in sync and the history on this computer; Cloud & Sync says so and keeps a Send anyway button for later. Without the history in step, chats cannot run on the other side either (see below). Free some space or change plan, and send it.

#Two computers

Another Mac can be connected to the same workspace. Each keeps its own copy. If two of them write to the same chat while they are apart, the copies are joined, not set aside: every message from both is kept, and the agent carries on from the branch that was active last. Until a connected computer has joined them, the cloud may list such a chat twice; it settles within seconds of any connected computer being online.

#The workspace's AI

While connected, the AI included in your workspace is available here too, on the same balance and with the same limits, in Settings → Models. It never replaces a provider you chose yourself. Disconnect removes it from this computer.

#A chat can run on either side

With the app on a computer and your cloud workspace together, every chat can run on either one, and you choose. A control in the line under the message box says where this chat runs: Cloud or This computer (in the cloud version your computer is listed by its name). Choose the other place and the chat runs there from the next message on, whichever of the two you type into.

Why: on your computer the agent works with the files and programs that live on it. In the cloud it keeps working when the computer is closed. A chat started on the computer can be handed to the cloud to run for hours; a chat in the cloud version can be handed to your computer.

• You stay where you are. The answer streams into the screen you typed on, with the stop button, steering and the agent's questions working as always. A chat that runs on the other side has a small cloud or laptop icon in the list.
• One place writes the chat. The place that runs the chat is the only one that writes it down; the other side gets it through sync, and the screen waits for it to arrive, usually a few seconds.
• The agent has what it needs. A chat is handed over only after the conversation, the agent's memory of it and the files attached to it have reached the place that will run it. A message sent a second after an upload waits for the file.
• If the other side is not there, the chat says so, keeps your message, and offers Run it here instead (which sends that message here) or Try again.

A chat can only be handed between your computer and your cloud, never from one computer to another. In Telegram, /here runs a chat on the side that is answering: for the shared bot that is the cloud, so it brings back a chat that was moved to a computer that is off.

#Letting the cloud run chats on your computer

This is off until you turn it on, in Eggent menu → Cloud & Sync… → Tasks from your cloud:

• Don't allow (the default). Your computer never runs anything for the cloud.
• Ask me for each chat. The first time the cloud wants to run a chat on your computer, the app shows which chat and the start of the message, and asks. An allowed chat stays allowed while you use it and for a day after. No answer within a minute means no.
• Allow every chat.

A chat run for the cloud works with the files and tools of your computer, exactly as a chat you started there. Allow only what you would start yourself. The question is the only thing between the cloud and your computer: the agent inside your workspace can ask for a chat too, so read what the dialog shows before you say yes, and keep in mind that Allow every chat removes the question.

The app shows the message as it will be run (and how much of it it left out), puts at most a few questions to you at a time, does not ask about a request the cloud has already given up on, and does not ask again for a few seconds about a chat you have just said no to. Allowing a chat covers the messages it sends later too. Turning this off disconnects the computer from the cloud's requests at once; chats you hand to the cloud from the computer keep working.

For a project that runs on a program of your own (Working on your own subscription) Ask me for each chat asks about it separately and names the program and how far it reaches. Allow every chat covers these chats too.

#Where a card runs

With the app on a computer paired with your workspace, a card on the task board can run on the computer as well as in the cloud. The card's Runs on says where: Cloud (the default: it keeps going while the computer is off) or your computer by its name, to work with the files and programs on it.

• The cloud starts every card, wherever it runs. A card for your computer is handed to it the way a chat is, so the app asks first unless you allowed every chat.
• A computer that is away does not fail a card. It waits in the queue, marked "… is away", and starts when the app is back and takes tasks from the cloud.
• Its chat runs there too. A message typed in the card's chat, on either side or from Telegram, runs where the card does. Moving the chat to the other side moves the card with it.
• A question, a stop and a refusal work as for any card: the question waits on the card in both places, Stop works from either side, and a computer that says no leaves the card waiting for you instead of asking again.

#Disconnect

Eggent menu → Cloud & Sync… → Disconnect. Files on this computer stay, but stop updating together with the cloud's; the workspace's AI stops working here, and the app works on its own again.

Disconnecting removes the pairing on this computer. It does not remove the computer from your workspace's list of devices yet; if you want that entry gone, write to support through the Help button in your workspace.

#If it does not connect

• "That login or password didn't work." Use the workspace's own login, the one you use in the browser.
• "No such workspace." Check the name: it is the part before .cloud.eggent.ai.
• "Sync isn't available for this workspace." It is not turned on for this workspace; write to support.
• "Couldn't reach the cloud." Check your connection and try again. If the title says can't reach the cloud afterwards, files are saved here and sent when the connection is back.
• "Too many attempts." Wait a minute.
• Files do not arrive. Look at the state in Cloud & Sync. If it says history is held back, that is the plan's room (see above); your files still sync.

#A chat will not run on the other side

• "… isn't available right now." The app is closed, offline, or Tasks from your cloud is off. Open the app, or choose Run it here instead.
• "… hasn't received this chat's latest changes yet." The files have not arrived. Wait a few seconds and send again; look at the sync state in Cloud & Sync.
• "… can't take this chat yet." The computer's chat history is not synced with the cloud.
• "… declined to run this chat." You, or the dialog's timeout, said no. Send again and allow it.
• "… can't run this chat right now. …" The project runs on a program (Working on your own subscription) and the program on that computer is not ready: signed out, not installed, or at its limit. Sort it out in the app on that computer, or run the chat here instead.
• "This chat was moved to this side a moment ago…" You moved the chat on the other side and wrote here before the sync carried the move over. Wait a few seconds and send again.
• Moving a chat says it has not arrived yet. Before a chat is moved, the side that moves it must hold what the other side last wrote. Wait a few seconds and try again.
• The answer stopped but the turn went on. If the line to the other side drops mid-turn, the turn carries on there and its answer appears here when the sync brings it.
• The computer went to sleep, or lost its connection, while it was working. The cloud notices after about a minute and says the connection was lost. The turn carries on there once the computer is back, and its answer appears here through sync. Stop works from either side.