Chats

A chat is the main way to work with Eggent. You write a task, the agent does it and shows what it is doing along the way: searching, reading, running commands, writing files.

#New chat

Press New Chat in the sidebar. The chat starts in the current project, or with the orchestrator if no project is selected. After the first message the chat gets a title and its own address, …/dashboard/<id>: bookmark it, open it in another tab or send it to your phone.

All chats of the current project are in the sidebar under Chats. To delete a chat, hover over it and press the delete icon.

#Attachments and images

• Attach a file with the paperclip button in the message box, or drag it into the window.
• A screenshot can be pasted straight from the clipboard (Ctrl+V / Cmd+V).
• Attachments are stored with the chat; the agent gets their path and can read them: text, PDF, Word, Excel, images, audio.

If a file is needed by the whole job rather than one chat, upload it to the project through the Files panel. See Files.

#The file beside the chat

When a file is open in the Files panel beside the chat, the agent is told which one with your message, so "fix the second paragraph here" means that file. Lines you select in it are sent too, and so is the block you pick on a page with Select. A line above the message box says what the agent sees; its cross stops it for that file until you open another one.

If the file has edits you have not saved, the agent is told so and asked not to change it under you. When the agent, a restore or the sync changes a file while you are editing it, the panel offers the new version instead of replacing your edits; whichever you keep, the other stays in the file's history.

#While the agent is working

The work belongs to the chat, not to the open tab:

• You can leave. Close the tab, open another chat, shut the laptop — the agent keeps going. A chat that is still being worked on has a dot next to it in the list.
• You can come back. Open the chat again and the answer keeps appearing from where it is now, not from the start.
• You can add to it. Type while the agent works and send: the message goes into the current task, and the agent reads it before its next step. Handy for corrections ("only in Chicago") without stopping the work. Until the agent has read it, it waits under the answer, marked as waiting; once read, it stands in the chat at the point where the agent read it. Several quick messages are read together. A file attached while the agent works goes with the next message, and the agent is told where it is. A command (a message that starts with /) can be sent once the work is over.
• You can stop it. The stop button beside the message box interrupts the work. Everything the agent has done and written so far is kept. A message it had not read yet stays in the chat with a Send button. You can also stop with a word: a message that is just "stop", "cancel" or "enough" (including from Telegram).

#When the agent asks

Sometimes the agent needs a decision from you: which option to take, confirming an action, a value to enter. A card appears in the chat with the question, buttons with ready answers and a field for your own answer. The agent waits and carries on from the same place. It waits up to a day: a question still unanswered after that ends the work, the question stays in the chat, and when you answer it later the agent picks up from there.

#Chat modes

Under the message box is the mode line. The mode decides how much of the workspace goes into every message, and it is chosen once, when the chat starts — it does not change afterwards. Need a different one? Open a new chat.

The light modes suit questions, translation, talking ideas through and working on a text: they are dozens of times cheaper. Real work with files, the web and documents needs the full mode.

#Choosing the model in a chat

Left of the send button is the name of the model that will answer the next message. Click it to change the model: inside a project the choice is saved for that project, in the orchestrator for the whole workspace. More in Models.

#Links and files in answers

When the agent mentions a file that exists, the path becomes a link: web pages, PDFs and images open in a new tab, anything else on the file's own screen. Audio files play right in the answer. Images the agent embeds in an answer are shown inline.

#Keys and passwords

Whatever you send is kept in the chat's history, and the agent sees it. When a message looks like a key, a token, a password or a private key, the chat says so before sending and offers Send anyway or Edit. A Telegram bot token and a model provider key have their own places — Settings → Messengers and Settings → Models — and the notice links to them.

Credentials are also masked in stored chats: after a reload, in the chat list, in what the agent reads when it looks at other chats and in the files that sync to your computer, a key shows as [hidden key]. The agent's own working memory of the conversation is not changed, so a key you gave it for a task keeps working. Only well-known shapes are masked (provider and cloud keys, bot tokens, bearer headers, private keys, links with a password in them, and a value kept under a name such as api_key or password in what the agent sent to a tool); a password inside ordinary text is not. A name written in code, like api_key = settings.client_key, is left alone — that is an example, not a key. Chats written before this are cleaned once, the first time the workspace starts after the update.

#Other chats

The agent can look into your other chats: list them, search them and read them. Ask "what did we decide about pricing last week?" or "what did this morning's report say?" and it finds the place. It can also move the conversation: in Telegram, "go back to the chat about the price list" switches there; in the browser it gives you the chat's link.

Chats with a clock icon were written by a scheduled task: one chat per task and day. Chats with an arrow are a project's work for another chat, started with @project — see Asking a project.

#Tips

• New task, new chat. A long history makes every next message more expensive and slower.
• If the agent heads the wrong way, stop it and say what is wrong — faster than waiting for the end.
• Leave long jobs running (visit 50 sites, process a folder of documents): the result will be in the chat and the files in the Files panel.